cancel
Showing results for 
Search instead for 
Did you mean: 

DB13 jobs failling

0 Kudos

Hi Gurus,

DB13 jobs are failling below are the details. Can you please let me know the reason behind job failing.

Thanks

Sambi

DBA:CHECK_DB

DBA:ANALYZE_TSP

DBA:NEXT_EXTENT

Job Log: DBA:CHECK_DB

Job started

Step 001 started (program RSDBAJOB, variant &0000000000032, user name AUTOSAP, language E)

Execute log. command SAPDBA on host witco-10

__Parameters: -check -u /

external program terminated with exit code 2

SAPDBA returned error status E

Job finished

Job Log : DBA:ANALYZE_TSP

Job started

Step 001 started (program RSDBAJOB, variant &0000000000030, user name AUTOSAP, language E)

Execute log. command SAPDBA on host witco-10

__Parameters: -analyze PSAP% -method CC -time 2 -T 10 -u /

SAPDBA: Method CC is not supported

Usage:

sapdba [ -u <userid>[/<password>]

-P <userid>/<coded_password>

-l <userid>[/<long_password>] / * transparent */

]

[ -p <profile> ]

[ -h[elp] ]

[ -r <dir> / * restart in batch */

-export <tsp_list> <table>

[-dest <path>

<tape_device> [-ta pe_size <size_in_M>] ]

-checkopt <tsp_list> <table>

[-threshold <n>] / * delta records in % */

[-T <hours>] / * time limit */

[-force] / * overwrite check res. */

-analyze <tsp_list> <table_list> <index> <file>

DBSTATCO NOOPTSTAT

[-method E C EI CI EH CH

[ -option P<n> R<m>] ] / * n in %, m in 1000 */

[-time <days>] / * refresh older than ... */

[-T <hours>] / * time limit */

-delete <tsp_list> <table> HARMF UL

-next <tsp_list> [-file <exception f ile>] [-test]

-check [-e <n>] / * number of extents */

-check_db_open

-sapr3 <pwd>

-alter_user <uid>/<pwd>

-init_sap_connect

-shutdown

-shutdown_abort

-startup

-startup_dba

-statistics ALL DBSTATCO <tables>

[-method E C EH CH

[ -option P<n> R<m>] ]

-sapsid <SID1>[,<SID2>,...]

-cleanup

-version

-verbose

-V -VERSION

]

external program terminated with exit code 2

SAPDBA returned error status E

Job finished

Job log :DBA:NEXT_EXTENT

Job started

Step 001 started (program RSDBAJOB, variant &0000000000031, user name AUTOSAP, language E)

Execute log. command SAPDBA on host witco-10

__Parameters: -next PSAP% -u /

ORA-01012: not logged on

(2011-02-05 08.00.30)

SAPDBA: Can't connect to ORACLE.

(2011-02-05 08.00.30)

SAPDBA - database not open or can't connect to ORA CLE

SAPDBA - exit status 2.

external program terminated with exit code 2

SAPDBA returned error status E

Job finished

Accepted Solutions (0)

Answers (1)

Answers (1)

markus_doehr2
Active Contributor
0 Kudos

> Job started

> Step 001 started (program RSDBAJOB, variant &0000000000032, user name AUTOSAP, language E)

> Execute log. command SAPDBA on host witco-10

> __Parameters: -check -u /

> external program terminated with exit code 2

> SAPDBA returned error status E

sapdba? What release is that? Must be ancient!

Markus

0 Kudos

Yes it is ancient one.

SAPDBA version : 4.6D (38)

release note 328375

kernel release 46D

patch date 2002-01-15

patch level 38

make platform rs6000

make mode OCI_805_32

make date Feb 5 2002

markus_doehr2
Active Contributor
0 Kudos

> SAPDBA version : 4.6D (38)

>

> release note 328375

> kernel release 46D

> patch date 2002-01-15

> patch level 38

> make platform rs6000

> make mode OCI_805_32

> make date Feb 5 2002

Nice )

Was this working before? If yes, what happened? Or is this a "new installation"? And you're using a 32bit 8.x database?

Markus

0 Kudos

This is old system. I am asigned to this systems few years back 2007 from that onwords these DB13 jobs are not working. Prepar to this I do not know.

markus_doehr2
Active Contributor
0 Kudos

> This is old system. I am asigned to this systems few years back 2007 from that onwords these DB13 jobs are not working. Prepar to this I do not know.

Well - before not even something about the system is known it's quite impossible to help.

Try the following as user <sid>adm:

svrmgrl
connect internal
select * from v$instance
file `which disp+work`
uname -a

Markus

0 Kudos

Hi have logged in as svrmgrl internal

Then select * from v$instance;Below is the result

1 NCQ witco-10 8.1.7.4.0 28-JAN-11 OPEN NO 1 STARTED ALLOWED NO ACTIVE PRIMARY_INSTANCE

witco-10:ncqadm 52> uname -a

AIX witco-10 2 5 0005444E4C00

witco-10:ncqadm 53> file `which disp+work`

/usr/sap/NCQ/SYS/exe/run/disp+work: executable (RISC System/6000) or object module not stripped

witco-10:ncqadm 54>

Edited by: Sambireddy Authu on Feb 7, 2011 7:53 PM

markus_doehr2
Active Contributor
0 Kudos

> Then select * from v$instance;Below is the result

>

> 1 NCQ witco-10 8.1.7.4.0 28-JAN-11 OPEN NO 1 STARTED ALLOWED NO ACTIVE PRIMARY_INSTANCE

>

>

> witco-10:ncqadm 52> uname -a

> AIX witco-10 2 5 0005444E4C00

> witco-10:ncqadm 53> file `which disp+work`

> /usr/sap/NCQ/SYS/exe/run/disp+work: executable (RISC System/6000) or object module not stripped

Ok - so we know now:

- AIX 5.2 32bit

- Oracle 8.1.7.4 32bit

- SAP kernel 46D 32bit

- you can connect internally

Can you execute (as ncqadm)

sapdba -u /

and please post the execution permissions of sapdba:

ls -l `which sapdba`

Markus

0 Kudos

Executed

witco-10:ncqadm 2> sapdba -u /ncqadm

SAPDBA: OS user must be ora<SID>.

(2011-02-07 10.12.14)

Also login as ora<sid> users and tried below the log

witco-10:orancq 2> sapdba -u orancq

Enter password (32 char. max.) for 'orancq' ==>

SAPDBA: OS user must be ora<SID>.

(2011-02-07 10.03.41)

witco-10:orancq 1> sapdba -u /ncqadm

SAPDBA: OS user must be ora<SID>.

(2011-02-07 10.14.51)

witco-10:ncqadm 78> ls -l `which sapdba`

-rwsrwxr-x 1 ncqadm sapsys 10633473 Oct 15 2002 /usr/sap/NCQ/SYS/exe/run/sapdba

markus_doehr2
Active Contributor
0 Kudos

> witco-10:ncqadm 78> ls -l `which sapdba`

> -rwsrwxr-x 1 ncqadm sapsys 10633473 Oct 15 2002 /usr/sap/NCQ/SYS/exe/run/sapdba

This seems to be your problem, the owner is wrong.

Try:

chown orancq sapdba
chmod 4755 sapdba

Then try again.

Markus

0 Kudos

If I execute is there any problem .

I am checking the same in development /Quality syste?

Please let me know

fidel_vales
Employee
Employee
0 Kudos

Hi,

in addition I think that someone has been "playing" with the SDBAC table as the error seems to be clear:

Step 001 started (program RSDBAJOB, variant &0000000000030, user name AUTOSAP, language E)

Execute log. command SAPDBA on host witco-10

__Parameters: -analyze PSAP% -method CC -time 2 -T 10 -u /

SAPDBA: Method CC is not supported

If you have another SAP system with the same version of R/3/Oracle/SAPDBA where the job works, then compare the entries.

Otherwise, look into SDBAC.

If this is correct, maybe someone has created the job incorrectly. Try to create it again