Question Re: Verify DB is getting failed in Technology Q&A

Verify DB is getting failed

Former Member — Fri, 22 Jan 2010 11:45:18 GMT

Hello Friends,

VerifyDB job which is scheduled from DB13 is getting failed.

Here are the job logs:

Job started

Step 001 started (program RSDBAJOB, variant &0000000000063, user ID SAPADMIN)

No application server found on database host - rsh/gateway will be used

Execute logical command BRBACKUP On host suesz086

Parameters:-u / -jid VERIF20100117100000 -c force -w only_dbv -p initP04001.sap -m ALL

BR0051I BRBACKUP 7.00 (27)

BR0055I Start of database backup: becjkgnk.dbv 2010-01-17 10.00.04

BR0484I BRBACKUP log file: /oracle/P04/sapbackup/becjkgnk.dbv

BR0477I Oracle pfile /oracle/P04/102_64/dbs/initP04001.ora created from spfile /oracle/P04/102_64/dbs/spfile.ora

BR0339E Number of parallel instances is differentfrom number of threads

BR0314E Collection of information on database files failed

BR0056I End of database backup: becjkgnk.dbv 2010-01-17 10.00.06

BR0280I BRBACKUP time stamp: 2010-01-17 10.00.06

BR0054I BRBACKUP terminated with errors

External program terminated with exit code 3

BRBACKUP returned error status E

Job finished

We are using the Oracle 10.2.0.4.0 on Linux machine

Can any one please suggest how to proceed for the troubleshooting.

Re: Verify DB is getting failed

former_member524429 — Fri, 22 Jan 2010 12:11:53 GMT

Hi,

Have you tried to run the same from OS level using BR*TOOLS ?

Regards,

Bhavik G. Shroff

Re: Verify DB is getting failed

Former Member — Fri, 22 Jan 2010 12:25:36 GMT

Hello,

Can you please check if the application server is up and running.

Re: Verify DB is getting failed

Former Member — Fri, 22 Jan 2010 12:29:14 GMT

Hi,

It must be a permission issue..

(I hope your BRTOOLS are updated one...)

There are 2 thing you need to check...

Permissions of BRTOOLS (brbackup, brarchive, brrestore, brspace etc.)

and the permission/owner of SAPDATAHOME (/oracle/SID/sapdataN)

somehow, brtools is not able to step into SAPDATAHOME directory or files have not read permission.

Please check the same and try again...

Regards.

Rajesh Narkhede

Re: Verify DB is getting failed

volker_borowski2 — Fri, 22 Jan 2010 12:34:58 GMT

BR0339E Number of parallel instances is differentfrom number of threads

Check your initSID.sap

Most likely, you did set parallel_instances while not runing RAC.

To utilize parallel DBV processes you need to set exec_parallel,

but do not set parallel_instances!

Volker

Re: Verify DB is getting failed

former_member524429 — Fri, 22 Jan 2010 12:46:24 GMT

Previously, you were able to perform VerifyDB job from DB13 ?

Have you applied New SAP kernel ?

If you have applied a new SAP Kernel , weather you hv executed "./saproot.sh <SID>" in the kernel directory as a part of Kernel patching activity ?

Regards,

Bhavik G. Shroff

Re: Verify DB is getting failed

former_member289039 — Sat, 23 Jan 2010 13:53:50 GMT

HI Mallesh,

Volker is right.

It seems parallel_instance parameter set in init<sid>.sap does not match with contents of table V$THREAD

check your initsid.sap parameter and correct it

Regards'

Jai

Re: Verify DB is getting failed

Former Member — Mon, 22 Feb 2010 18:27:32 GMT

Hi,

parameter parallel_instances value in INIT<SID>.sap and the contents of V$THREAD are pasted below.

how to compare those two values. and suggest if i need to change the value.

Please include the local instance in the parameter definition!

default: no parallel instances
example for initRAC001.sap:
parallel_instances = (RAC001:/oracle/RAC/920_64@RAC001,# RAC002:/oracle/RAC/920_64@RAC002, RAC003:/oracle/RAC/920_64@RAC003)

and the contents of V$THREAD as follows

THREAD# STATUS ENABLED GROUPS

INSTANCE

OPEN_TIME CURRENT_GROUP# SEQUENCE# CHECKPOINT_CHANGE# CHECKPOINT_TIME

ENABLE_CHANGE# ENABLE_TIME DISABLE_CHANGE# DISABLE_TIME

LAST_REDO_SEQUENCE# LAST_REDO_BLOCK LAST_REDO_CHANGE# LAST_REDO_TIME

1 OPEN PUBLIC 6

P01001

03-FEB-10 16 2964 379779688 22-FEB-10

THREAD# STATUS ENABLED GROUPS

INSTANCE

OPEN_TIME CURRENT_GROUP# SEQUENCE# CHECKPOINT_CHANGE# CHECKPOINT_TIME

ENABLE_CHANGE# ENABLE_TIME DISABLE_CHANGE# DISABLE_TIME

LAST_REDO_SEQUENCE# LAST_REDO_BLOCK LAST_REDO_CHANGE# LAST_REDO_TIME

60921282 10-SEP-08 0

2964 216133 379862520 22-FEB-10

THREAD# STATUS ENABLED GROUPS

INSTANCE

OPEN_TIME CURRENT_GROUP# SEQUENCE# CHECKPOINT_CHANGE# CHECKPOINT_TIME

ENABLE_CHANGE# ENABLE_TIME DISABLE_CHANGE# DISABLE_TIME

LAST_REDO_SEQUENCE# LAST_REDO_BLOCK LAST_REDO_CHANGE# LAST_REDO_TIME

2 OPEN PUBLIC 6

P01002

03-FEB-10 22 1827 379766137 22-FEB-10

THREAD# STATUS ENABLED GROUPS

INSTANCE

OPEN_TIME CURRENT_GROUP# SEQUENCE# CHECKPOINT_CHANGE# CHECKPOINT_TIME

ENABLE_CHANGE# ENABLE_TIME DISABLE_CHANGE# DISABLE_TIME

LAST_REDO_SEQUENCE# LAST_REDO_BLOCK LAST_REDO_CHANGE# LAST_REDO_TIME

60921282 10-SEP-08 0

1827 259157 379862517 22-FEB-10

Re: Verify DB is getting failed

peter_dzurov — Tue, 23 Feb 2010 02:09:21 GMT

Please check Note 905359 - Using BR* tools for Oracle RAC databases and compare your settings.