Oracle executable file permission

BRBACKUP fails with the following error messages, for example:
BR0051I BRBACKUP 7.00 (20)
BR0055I Start of database backup: bddzbuxf.ant 2009-11-10 10.12.35
BR0280I Time stamp 2009-11-10 10.12.36
BR0301W SQL error -1031 at location BrLicCheck-7
ORA-01031: insufficient privileges
BR0301W SQL error -942 at location BrbDbLogOpen-1
ORA-00942: table or view does not exist
BR0324W Insertion of database log header failed
BR0280I Time stamp 2009-11-10 10.12.37
BR0301E SQL error -1031 at location BrCntrlCopy-1
ORA-01031: insufficient privileges
BR0320E Copying of control file to ... failed
BR0314E Collection of information on database files failed
BR0056I End of database backup: bddzbuxf.ant 2009-11-10 10.12.37
BR0280I Time stamp 2009-11-10 10.12.37
BR0054I BRBACKUP terminated with errors

select grantee,granted_role from dba_role_privs where grantee='OPS$BIPADM';
select grantee,granted_role from dba_role_privs where grantee='OPS$BIQADM';
SQL> connect /
ERROR:
ORA-27140: attach to post/wait facility failed

SQL> connect /as sysdba
ERROR:
ORA-09925: Unable to create audit trail file
Linux-x86_64 Error: 13: Permission denied
Additional information: 9925
ORA-09925: Unable to create audit trail file
Linux-x86_64 Error: 13: Permission denied
Additional information: 9925
Note 400241 - Problems with ops$ or sapr3 connect to Oracle
Note 50088 - Creating OPS$ users on Windows NT/Oracle
https://forums.oracle.com/forums/thread.jspa?threadID=384361

Number range error after client copy

Problem:
--------
This message "xpress document "Update was terminated" received from author
" is coming while trying to post any FI documents.
Solution
----------
1: Check the details in SM13 transaction.
You can check reason for update termination in SM13.
2:  Most common cause for this error relates to the document number range
Please refer
http://help.sap.com/saphelp_nw04/helpdata/en/95/3d5540b8cdcd01e10000000a155106/content.htm

Restated the SAP application and the nubmer range buffer was cleaned.and the error did not came

SXPG_COMMAND_EXECUTE failed for BRBACKUP

My online backup has been scheduled in DB13
when its reach the backup time its showins error.

Status : Scheduled failed
JOB LOG:
30.11.2012 17:26:56 Job started
30.11.2012 17:26:56 Step 001 started (program RSDBAJOB, variant &0000000000672, user ID BASIS)
30.11.2012 17:26:56 No application server found on database host - rsh/gateway will be used
30.11.2012 17:26:56 Execute logical command BRBACKUP On host PRODORADB
30.11.2012 17:26:56 Parameters:-u / -jid ALLOG20121130172655 -c force -t online -m all -p initPDR.sap -a -c force -p initPRD
30.11.2012 17:26:56 offsite.sap -cds
30.11.2012 17:27:28 SXPG_STEP_XPG_START: is_local_host: rc = 403
30.11.2012 17:27:28 SXPG_STEP_XPG_START: host = ECCDB
30.11.2012 17:27:28 SXPG_STEP_XPG_START: is_local_r3_host: rc = 802
30.11.2012 17:27:28 SXPG_STEP_XPG_START: RFC_TCPIP_CONNECTION_OPEN: rc = 1003
30.11.2012 17:27:28 SXPG_STEP_COMMAND_START: SXPG_STEP_XPG_START returned: 1.003
30.11.2012 17:27:28 SXPG_COMMAND_EXECUTE(LONG)
30.11.2012 17:27:28 = 20121130172728
30.11.2012 17:27:28 COMMANDNAME = BRBACKUP
30.11.2012 17:27:28 ADDITIONAL_PARAMETERS =
30.11.2012 17:27:28 -u / -jid ALLOG20121130172655 -c force -t online -
30.11.2012 17:27:28 m all -p initPRD.sap -a -c force -p initIRP
30.11.2012 17:27:28 PRD.sap -cds
30.11.2012 17:27:28 LONG_PARAMS
30.11.2012 17:27:28 OPERATINGSYSTEM = ANYOS
30.11.2012 17:27:28 TARGETSYSTEM = PRODORADB
30.11.2012 17:27:28 DESTINATION
30.11.2012 17:27:28 SY-SUBRC = 1003
30.11.2012 17:27:28 SXPG_COMMAND_EXECUTE failed for BRBACKUP - Reason: program_start_error: For More Information, See SYS
30.11.2012 17:27:28 Job cancelled after system exception ERROR_MESSAGE

Solution:
--------
Refer to note 446172 : Note 446172 - SXPG_COMMAND_EXECUTE (program_start_error) in DB13
Note 34219 - DB13: CPIC error CM_RESOURCE_FAILURE_RETRY
Note 853610 - Configuring transaction DB13C for Oracle
http://help.sap.com/saphelp_nw70/helpdata/en/c4/3a7fbb505211d189550000e829fbbd/content.htm

The gw/remsh = rsh in rz11
SAP application server : ECCCI
Database server : ECCDB
From ECCCI I execute rsh ECCDB and it was giving error.
I activate rsh in ECCDB and execute rsh ECCDB date and it was successful.
RFC : SAPXPG_DBDEST_ECCDB was giving error
After activating rsh this rfc was successful.

Stop SAP does not work

When I executed the command stopsap r3 It did not stop the SAP application.
It did not kill the sapstart and dw work process.

Solution:
In the dir /usr/sap/ND1/DVBMGE17/work kill.sap was there but no entry was there.
Generally it stores the PID of sapstart
Then I did : ps -ef | grep sapstart
get the PID
and add this in kill.sap
echo "kill -2 <PID of sapstart>" > kill.sap
and it successfully stopped.
Actually during stopsap it searches for kill.sap and do the entry in it

Upgrade in Distributed system

During upgrade to EHP5 on ECC landscape the system did not come up in downtime phase after the kernel switch and repository import to main instance from shadow instance.

This problem occurs generally in distributed system i.e ASCS instance and Central instances are on different hosts.The kernel switch occurs in /usr/sap/<SID>/SYS/exe/run to 720 version and also in /usr/sap/<SID>/DV*/exe by the kernel file sapcpe.

But that did not happen in ASCS instance . So I have to mannualy copy all the execucutables from
/usr/sap/<SID>/SYS/exe/run  to /usr/sap/<SID>/ASCS00/exe.

And then execute the SAPup again where it was stopped and it worked fine.

Manual checks before starting Technical Downtime

Database and IS specific preparation
--------------------------------------------

• Deactivaion of cluster failover during the technical downtime
• Free memory space avalable for the database
• rrequired memory space avalable in F.S
• Automatic restart of SAP system is deactivated
• Dattabase statistics is updated

SAP system side preparation.
------------------------------------

• All functional that is bussiness-critiacal, background jobs are complete and planned.
• Outstanding updates are processed.
• Setting up a system messsage (SM02) with the inforamtion that system is unavaliable
• No SAP object locked by repairs
• consistence check (missing table and indexes ) successful (DB02)
• Background jobs of class C configurred for CI
• RDDIMPDP background job configurred for CI
• Batch process configured for CI
• Locking of SAP users
• No active users logged into the system
• No open or aborted updates in system(SM13)
• BW delta queues processed (SMQ1)
• General : interface gueues cleaned (LBWG)
• Monitoring tools ( application server and CI) stoipped during downtime.
• Isolation of CI (stopping the application servers)
• Take a complete offline database backup( better if you take F.S backup of /oracle directoty)
• Consisttent backup of installation directory,of the kernel directory and SAP profiles avaliable as they will be overwritten during downtime. 

Administration of shadow instance

In SAPehpi a shadow instance is created that runs in parrallel to live instance while you implement the modification adjustment (SPDD) and then start the activation.The last activity of shadow instance is the removal of activation error.

There are situation in which you need to intervene the installation routine like starting,stopping,locking and unlocking of shadow instance.

Starting the shadow instance
-----------------------------------
Go to installtion directory /EHPI/ABAP/BIN. Use the command ./SAPehpi startshd start the shadow instance.

Stopping the shadow instance
-----------------------------------
Go to installtion directory /EHPI/ABAP/BIN. Use the command ./SAPehpi stopshd stop the shadow instance.Note that shadow instance only runs between the phases STARTSHDI_FIRST and STOPSHDI_LAST.Logging on to the shadow instance is only for modification adjustment and removing activation error.

Unlocking the shadow instance
--------------------------------------
A manual unlocking of the shadow insttance is required for removing the activation error.
cd /EHPI/abap/bin
./SAPehpi unlockshd <SAPSID>

Locking the shadow instance
-----------------------------------
Manual locking of shadow instance is imperative after the manual unlocking before you continue the installation routine.
cd /EHPI/abap/bin
./SAPehpi lockshd <SAPSID>

Unlocking the system and the development environment
--------------------------------------------------------------------
In exceptional cases( for example support cases) you must unlock the instnce and undo a transport lock, if refquired . To do this call the following commands

tp unlocksys <SAPSID> pf=<path to transport profile >/tpprofile
tp unlock_eu <SAPSID> pf=<path to transport profile >/tpprofile

Use this command only if the support team explicitily request you do so.
The unauthorised import of transport after an official lockins of the development env by EHPI means that you can bring your system to an incostitent state, you may lose your support claim.

Locking the system and the development environment
-----------------------------------------------------------------
Always lock your system again before you continue the installation routine using the command

tp locksys <SAPSID> pf=<path to transport profile >/tpprofile
tp lock_eu <SAPSID> pf=<path to transport profile >/tpprofile