cancel
Showing results for 
Search instead for 
Did you mean: 

DB13 Job fail with error :Database instance is shut down

Former Member
0 Kudos

Hi All,

Recently we upgraded our Redhat Linux, Database from 9i to 10.2.0.4 and SAP Kernel 640 to patch 347.

Now my system is working fine but in DB13 jobs I am getting error:

Job started

Step 001 started (program RSDBAJOB, variant &0000000000763, user ID SHMITTAL)

Execute logical command BRCONNECT On host saturn

Parameters: -u / -c -f stats -t ALL

BR0801I BRCONNECT 6.40 (52)

BR0805I Start of BRCONNECT processing: cegcuesi.sta 2011-06-16 06.26.52

BR0484I BRCONNECT log file: /oracle/PP0/sapcheck/cegcuesi.sta

BR0613E Database instance PP0 is shut down

BR0806I End of BRCONNECT processing: cegcuesi.sta2011-06-16 06.26.52

BR0280I BRCONNECT time stamp: 2011-06-16 06.26.52

BR0804I BRCONNECT terminated with errors

External program terminated with exit code 3

BRCONNECT returned error status E

Job finished

it is looking to me that somewhere still Oracle path is mentioned as of 9i version.

I checked environment variables, Default profile, initSID.sap but not find any issue, checked on google it says check tnsnames.ora, I checked that file but there is no such parameter for Oracle home.

Please suggest to resolve the issue.

Shivam Mittal

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Issue Resolved by setting permission in /oraclehome/bin

Oracle file to -rwsr-s--x

Note 583861 - UNIX: Errors due to Oracle executable

volker_borowski2
Active Contributor
0 Kudos

BR0801I BRCONNECT 6.40 (52)

Hi,

allthough I am not quite sure, because 9i is sooo old and 10.2 is even near out of maintanance,

...

Kernel 6.40 is linked against a version 9 client thus forcing sidadm to work with a 9i environment.

brtools 6.40 working as orasid (environment 10g)

and failing as sidadm (in the 6.40 plain kernel environment (oracle 9i))

is perfectly normal as far as I remember.

I think there was a section in the version 10 upg-guide whichg says to switch brtools to version 7.0, even if you use a 6.40 kernel exactly for this reason. This is, because version 7.0 brtools are hardlinked against the instantclient 10.

So these work even as sidadm with an environment set to a version 9 client.

I can not verify exactly, any more, cause all our 6.40 systems have recently gone to oracle version 11

requireing the switch to the 6.40 EX2 kernel and brtools 7.20.

Try brtools 7.00 on current patchlevel.

Volker

Former Member
0 Kudos

Hi Shivam,

What happenning if you execute the same command on ora<sid> user? If you are not facing with the problem, check the note 583861 for permissions.

Additionally, check whether you executed "./saproot.sh"

Best regards,

Orkun Gedik

Former Member
0 Kudos

Look in this file or post it:

log file: /oracle/PP0/sapcheck/cegcuesi.sta

Former Member
0 Kudos

File says ; same as I pasted

BR0801I BRCONNECT 6.40 (52)

BR0805I Start of BRCONNECT processing: cegcuesi.sta 2011-06-16 06.26.52

BR0484I BRCONNECT log file: /oracle/PP0/sapcheck/cegcuesi.sta

BR0613E Database instance PP0 is shut down

BR0806I End of BRCONNECT processing: cegcuesi.sta 2011-06-16 06.26.52

BR0280I BRCONNECT time stamp: 2011-06-16 06.26.52

BR0804I BRCONNECT terminated with errors