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.

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/

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

Procedure to check.

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

2. execute statement to check limit of failed login attempts.

SELECT LIMIT FROM DBA_PROFILES
WHERE
PROFILE = ‘DEFAULT’ AND
RESOURCE_NAME = ‘FAILED_LOGIN_ATTEMPTS’;

default limit = 10.

Changing default limit = 10 to unlimited.

ALTER PROFILE DEFAULT LIMIT FAILED_LOGIN_ATTEMPTS UNLIMITED;

now it’s time to change the password of SAPSR3.

CMD>brconnect -u / -c -l E -f chpass -o SAPSR3  -password (whatever_you_want)

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.

Procedure to resolve:

The sapstartsrv.exe file is not updated in C:\WINDOWS\system32. (after kernel upgrade)

The resolution is to copy the latest file from /SID/exe of the upgraded kernel and paste and overwrite the one existing in C:\WINDOWS\system32 and then restart the Services and SAP.

The dialog queue appeared and the issue resolved.

Hope this helps..

Question: In SP01 what is the difference between print directly & print with changed parameters?

1)     The setting that uses spool with “Print directly to the printer.” You might choose this setting if you have a lot of jobs waiting in the spool and want to print something else in a hurry, and is defined for the user-id
For Print a Spool Request with changing its Parameters.
To change the request before printing it, for example, to send the request to a different printer or change the number of copies to print, choose Print with changed parameters. You can change the following settings before printing:
a) Output Device: If possible, only send the output to an output device that uses the same device type as the output device for which the request was originally created. The device type indicates the printer type used, such as PCL.
b) Start Time: To set a later time for printing, choose this button

Question: If a spool request is in waiting status for a long time, what does it mean?

2)     Status Waiting may also indicate that there is a problem with the spool work process that is assigned to a printer. Check the following:

a) Find out which printer an output request has been sent to. To do this, select the relevant spool request in the Output Controller and choose. You can find the printer name in the Output device field.

b) Find out which spool work process is responsible for the printer. Enter the name of the printer to which the output request was sent in the Output Device field on the Devices/serverstab and choose enter. Display the definition and note the SAP application server name that appears in the Print server field. If you have only a single spool server in your SAP system, then you can omit this step.

c) Use the CCMS System Monitor or in transaction SM51 to display the application servers in your SAP system. Check that the application server that you noted from the Print server field is running and that the server offers the service Spool. If the server is not running or if the Spool service is not active, then you have found the source of the problem.

d) If the print server is running and the spool service is active, then check the activity in the spool work process.

In transaction SM51, mark the print server in question and click on Processes. In the process display, look for the spool work process and note the name of the active user. If User SAPSYS is active, this indicates that the spool work process is busy with internal spool activities or is requesting the status of a print request from a host spool system. Choose CPU repeatedly to check the CPU time that the spool work process requires. If the same CPU time is always displayed, then it is likely that the spool work process is waiting for a status query to time out. It is likely that you have to then find the reason for the delay in output request processing.

Question: If a user wants to reprint his document again what should to do ?

3)  The user needs to give the spool request number in sp01 and then print it or Users should have Tx SP02 for their own spool requests (not SP01 which is a BASIS Tx). User can browse & reissue an output request for a particular spool (unless they deleted it, or it time expired and got reorg’d).

Question: What I have done to use users OS level printer as SAP printer. I mean if a user has given a print if SAP couldn’t able to find printer it will be in error status. In this case I want to reprint that document from users OS level default printer.

4) There are two things for this:
a) You have to define the local printer same as for your OS in SAP and maintain that as local in spad.
b) The user needs to give the spool request number in sp01 and then print it going forward.

or

You could configure a front-end printer (host spool method G) in SPAD. Printer name is generally LOCL. Understand now that you will have more problems by introducing front-end printing, and not fewer. Users will become accustomed to using it and will insist you fix it when some desktop patch or network change breaks it. I know it SEEMs like a good idea; remember I tried to warn you. Host spool method M is a more easily supported alternative (print-to-email and they can use the resulting attachment as they like).

Question: What are the regular spool problems and resolutions?

5) Many and varied. Users do not typically distinguish between ‘spool problems’ and ‘printing problems’. Make sure the housekeeping jobs run: https://service.sap.com/sap/support/notes/1411877

Question: In my project I had faced a prob in SOLMAN. The system was giving short dump “SPOOL_INTERNAL_ERROR” and while checking it, system was issuing message “SPOOL OVERFLOW”.

6) As the solution I applied resolution provided in SNote no. 48284, which asked me to raise the upper limit for spool requests using TC=SNRO. The complete procedure is:

1. Log on to the system in client 000 and call transaction SNRO.

2. Select the object SPO_NUM and choose the button: Number ranges.

3. On the next screen, choose: Change Intervals.

4. In the “To number” column, change the upper limit of interval 01 to 999,999, for example.

Question: Sometime printing is working perfectly & then suddenly all printing get stop. We have seen in SAP spool error log is:

“Unable to open file /usr/sap/<SID>/DVEBMGS40/data/009v1WwD.<SID> for writing (error 28)

Errors occurred processing this print request

There may be no printout”.

 After restarting it works fine for some time but again printing got stuck.

7) There are 2 things for this:

a) Do TemSe reorganization; remove inconsistencies & Restart SPO processes in SM50.

b) Error in UNIX Index Nodes (Inode stores basic information about a regular file, directory, or other file system object.)

We were facing out of index nodes issue. The directory where all the batch logs were getting accumulated had run out of number of files it could accommodate even though space was available. When we moved the batch logs to another directory issue was resolved.

More will come soon.

Source: help.sap.com

Service Desk is easy to configure rather then ChaRM. I have completed my Service Desk configuration successfully & it’s working smoothly. Here i will not provide any steps due to it’s a very long configuration, however if you required the configuration steps, you can mail me directly at my adil(at)adilfahim.com

ChaRM is little bit difficult to configure. I didn’t find any standard configuration document in SAP service market place then i searched on SDN and find some different docs, compiled that docs & create a single document to work around. i have completed almost all steps which required in ChaRM but still i am stuck while creating Change Request to add in Maintenance Cycle. When i will completed, i will update my blog and will share a doc of fully configured ChaRM Configuration.

I got stuck after changing Portal — User Management — Identity Management — Data Source —- Database only to ABAP System.

After restarting the instance the value of Data Source shows only ABAP system & for somehow if you want to revert to Database only, it’s not possible. There is no any other options rather than ABAP System.

As per SAP note 718383.

dataSourceConfiguration_abap.xml

No change is possible.

This configuration supports all usages (especially SAP Exchange Infrastructure and SAP Enterprise Portal) by making ABAP users and ABAP roles available as users and groups in the UME, and supports the creation of new groups in the UME (which are then stored in the local database) as well.

The below SDN thread talks about same issue:

http://forums.sdn.sap.com/thread.jspa?messageID=10568533

SOLUTION:

You can change the database only(default) option by editing UME properties in Config Tool.

Steps to follow:

·         Config Tool — Global server configuration – services – com.sap.security.core.ume.service

·         ume.persistence.data_source_configuration (Make this value Restore to Default)

·         Restart the instance.

Now when you check again in Portal— User Management — Identity Management — Data Source

It will show the Database only(Default) value.

Enjoy!