SAP workprocesses can not connect to the database any more.

SAP Note 1519872 

Symptom

This note describes the configuration of an SAP installation with the SAP-pecific database user profile SAPUPROF.

Symptom:
SAP system does not start any more.
SAP workprocesses can not connect to the database any more.

SAP trace files contain errors similar to the following:
TRACE-INFO: 101:  [    dbsloci.,00000]  *** ERROR => CONNECT failed with sql error ‘28001’
TRACE-INFO: 102:  [     dev trc,00000]     set_ocica() -> SQL error code 28001
TRACE-INFO: 103:  [     dev trc,00000]    >oci_get_errmsg (con_hdl=0,rc=28001)
TRACE-INFO: 104:  [     dev trc,00000]     OCIErrorGet -> SQL error code: 28001
TRACE-INFO: 105:  [     dev trc,00000]     ORA-28001: the password has expired

Other symptoms:
You get ORA-28000 or ORA-28001 or ORA-28002 errors when you try to connect to the database (i.e. as database user SYSTEM).

Reason:

  • Oracle Database Release 11.2.0.X.
  • Database user profile SAPUPROF is not configured. Check this with the following query (for user SAPSR3):
    SQL> select profile from dba_users where username = ‘SAPSR3’;
  • With 11.2, passwords of database users must be changed every 180 days for security reasons.

For full solution, Please go through this note 1519872.

Free Screen Capture for Windows 7

After upgrading my laptop from Win XP to Win 7, I was unable to use ZAPGRAB as there is a compatibility issue with Win 7. For working in Win 7 you need to download the LICENSED version of ZAPGRAB. I have found many free screen captures programs on internet that can fulfill my requirements as ZAPGRAB do but didn’t find any good one.

After a lot of searching I have found “Greenshot” which is better than others & can also use in WIN 7. It’s an open source program.

Here is an download link of Greenshot official site http://getgreenshot.org/downloads/

Control file and its functions in Oracle.

Control file and its functions in Oracle

This article answers the following queries :
•         What is the control file in oracle?
•         What are the functions of control file in oracle?
•         What are the control file contents ?
•         Can database function properly without control file?
•         Can we edit control file
•         Who can modify control file?
•         At what time control file will be created?

What is control file in Oracle and what are its functions ?
Control file is a small binary file which is necessary for the database to start and operate successfully.

What are the functions of control file ?
Each control file is associated with only one database.  Oracle continuously updates control file during database use so this file must be available for writing whenever the database is in the open state.  Control file will be created at the same time of database creation.
Whenever a datafile or a redolog file is added to, dropped or renamed in the database, the control file is updated to reflect the physical structural change.
These changes are recorded in control file which facilitates:
>   Oracle to identify the files that are required or available in case database recovery is needed
>   Oracle to identify the datafiles and redolog files to open during database startup.

Can database function properly without control file?
No. Database cannot function properly if the control file is not available.

Can we edit control file? Who can modify control file?
Please note control file cannot be edited by database administrator or by any user. Control file information can only be modified by Oracle.

Contents of control files :
> Control file contains information such as
>   Database name
>   Timestamp of database creation
>   Tablespace information
>   The log history
>   Archive log information
>   Current log sequence number
>   Checkpoint information
>   Names and locations of associated datafiles and redolog files
>   Datafile copy information
>   Datafile offline ranges
>   Backup set and backup related information
>   Backup datafile and redolog information

SAPSR3 user locked.

Recently we find an issue that while starting SAP via SAP MMC, work process stop in Ended status. We found in developer trace that it’s a database connectivity issue. In some cases connectivity from SAP to Database does not happen due to SAPSR3 user locked.

Steps to find the issue in Windows Environment.

1. Go to CMD – R3trans -d (it ended with return code 0012)

2. Read the trans.log & search if there any user lock issue found.

if YES then go to below procedure to resolved.

1. Stop the SAP process in SAP MMC.

1. go to sqlplus via “CMD – sqlplus / as sysdba

2. execute statement to check which user(SAPSR3) is locked.

select username, account_status from dba_users;

find the list of dba users with their status. if SAPSR3 user is locked then execute this below statement to unlock.

alter user SAPSR3 account unlock;

again execute to check whether it’s successful or not.

select username, account_status from dba_users;

if successful log out from SQL & execute “R3trans -d“. it finish with RC=0000.

START SAP & it will start.