DB-13 Error ( checkdb )

Hello Gurus,
In T-Code DB-13, I created some Jobs example like checkdb, update stats, etc etc
while running this jobs giving me this error can anybody tell me what is the rectification or what is a needful to solve this problem
Job started
Step 001 started (program RSDBAJOB, variant &0000000000099, user ID CSCADMIN)
Execute logical command BRCONNECT On host bascop26
Parameters: -u / -jid CHECK20070608095728 -c -f check
BR0801I BRCONNECT 7.00 (11)
BR0477I Oracle pfile /oracle/QBW/102_64/dbs/initQBW.ora created from spfile /oracle/QBW/102_64/dbs/spfileQBW.ora
BR0280I BRCONNECT time stamp: 2007-06-08 09.57.33
BR0301E SQL error -942 at location BrLicCheck-32
ORA-00942: table or view does not exist
BR0806I End of BRCONNECT processing: cdvlajpr.log2007-06-08 09.57.33
BR0280I BRCONNECT time stamp: 2007-06-08 09.57.33
BR0804I BRCONNECT terminated with errors
External program terminated with exit code 3
BRCONNECT returned error status E
Job finished

Hi,
This error occurs due to the sapdba permission in the oracle database.
Please import the role sapdba_role.sql according as per the SAPnote : 134592 and also apply this note 834917.
Hope this resolves your problem
Regards,
Maheswaran J

Similar Messages

Sql server 2005, R/3 4.6c and compability mode

Hi
I doing upgrade from 4.6c --> ECC 6.0 on sql server 2005. And i get followin error
SCRIPT MSSINCHK
=================
Msg 468, Level 16, State 9, Server MEDIASP10, Line 55
Cannot resolve the collation conflict between "SQL_Latin1_General_CP850_BIN" and
"SQL_Latin1_General_CP850_BIN2" in the equal to operation.
Msg 468, Level 16, State 9, Server MEDIASP10, Line 66
Cannot resolve the collation conflict between "SQL_Latin1_General_CP850_BIN" and
"SQL_Latin1_General_CP850_BIN2" in the equal to operation.
Execution completed successfully
I have checked that collation order is correct.
I think that problem that somehow sql server's compability mode is recognized wrong (sql server 2000 insted sql server 2005).
Any colution on this ?
Br, Juha Niemi

Hi there,
I'm running into this same issue when trying to run PREPARE for the 4.6c to ERP/ECC 6.0 upgrade in phase INITPUT_PRE. I ran several of the queries mentioned in this thread and discovered that the database and instance are both BIN2, and 116230 columns are BIN2, but another 319398 columns are still BIN. Without reverting the database (eek, somehow) back to MSSQL2000 and rerunning instcoll.exe (again, I already did once) or building an alter table query for each one that is out of spec (which according to MSDN won't work on certain cols anyway), how can this be resolved?
for my SID database I have the following column types in count:
SQL_Latin1_General_CP850_BIN2     116230
Latin1_General_BIN     29
NULL     58467
Latin1_General_CI_AS_KS_WS     11
SQL_Latin1_General_CP850_BIN     319398
But the databases are all running BIN2 as such:
Server     SQL_Latin1_General_CP850_BIN2
Master     SQL_Latin1_General_CP850_BIN2
Model     SQL_Latin1_General_CP850_BIN2
TempDB     SQL_Latin1_General_CP850_BIN2
SID     SQL_Latin1_General_CP850_BIN2
The checkdb procedure came back with no errors:
CHECKDB found 0 allocation errors and 0 consistency errors in database 'PD1'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
And the system appears to be functioning correctly, except that the Upgrade Assistant won't let me continue with the mismatched column collation types.
Suggestions? I noticed there was never a resolution posted.
Thanks,
--ben

Recover SQL Server database from SUSPECT mode

Hi Expert DBAs,
As I know the database should be restored from backup and logs reapplied. That’s the first and generally recommended approach any time a DB is suspect, whether it’s from log or data file corruption.
But if I have no backups then we follow below steps ( after Googling I found these steps on most of the websites ):
1.EXEC sp_resetstatus ‘yourDBname’;
2.ALTER DATABASE yourDBname SET EMERGENCY
3.DBCC checkdb(’yourDBname’)
4.ALTER DATABASE yourDBname SET SINGLE_USER WITH ROLLBACK IMMEDIATE
5.DBCC CheckDB (’yourDBname’, REPAIR_ALLOW_DATA_LOSS)
6.ALTER DATABASE yourDBname SET MULTI_USER
Now my question is,
1. If after executing DBCC CHECKDB at 3rd step, it shows inconsistency.Then I will execute SET SINGLE USER WITH ROLLBACK & if after executing DBCC CHECKDB at 3rd step, no errors found. Then what will be the steps?
2. When we execute DBCC CHECKDB (' DBNAME ', REPAIR_ALLOW_DATA_LOSS) how can we recover lost data during process.As far as I know some data will loss and if it will happen then business will get suffered.
3. Why run DBCC CHECKDB() WITH REPAIR_ALLOW_DATA_LOSS if there are no consistency errors in the database?
I am stucked in these questions....
Regards,
Yashwant Vishwakarma | SQLOcean.com
Yashwant Vishwakarma | www.sqlocean.com

There is no easy or same steps, it all depends on what error and what caused suspect.
Example is below:
http://www.sql-server-performance.com/2015/recovery-sql-server-suspect-mode/
2) Straight answer would be no you cant recover if no backup. Again it all depends what error checkdb returns and some things can be tried as explained earlier but no guarantee.
The REPAIR_ALLOW_DATA_LOSS option is not the best option for bringing a database to a physically consistent state. If successful, the REPAIR_ALLOW_DATA_LOSS option may result in some data loss. In fact, it may result in more data lost than if a user were to
restore the database from the last known good backup. Microsoft always recommends a user restore from the last known good backup as the primary method to recover from errors reported by DBCC CHECKDB. The REPAIR_ALLOW_DATA_LOSS option is not an alternative
for restoring from a known good backup. It is an emergency “last resort” option recommended for use only if restoring from a backup is not possible.
Certain errors, that can only be repaired using the REPAIR_ALLOW_DATA_LOSS option, may involve deallocating a row, page, or series of pages to clear the errors. Any deallocated data is no longer accessible or recoverable for the user, and the exact contents
of the deallocated data cannot be determined. Therefore, referential integrity may not be accurate after any rows or pages are deallocated because foreign key constraints are not checked or maintained as part of this repair operation. The user must inspect
the referential integrity of their database (using DBCC CHECKCONSTRAINTS) after using the REPAIR_ALLOW_DATA_LOSS option.
https://msdn.microsoft.com/en-us/library/ms176064.aspx

Recommended Recovery Options for Corrupt Objects

Hello ,
When I ran DBCC CHECKDB on one of my databases, I noticed few objects being corrupt.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:915964) allocated to object ID 1105439012, index ID 1, partition ID 72057594129612800, alloc unit ID 72057594152419328 (type LOB data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 1105439012, index ID 1, partition ID 72057594129612800, alloc unit ID 72057594152419328 (type LOB data). The off-row data node at page (1:915964), slot 0, text ID 1910439936 is referenced by page (1:914286), slot 0, but was not seen in
the scan.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:915966) allocated to object ID 1105439012, index ID 1, partition ID 72057594129612800, alloc unit ID 72057594152419328 (type LOB data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 1105439012, index ID 1, partition ID 72057594129612800, alloc unit ID 72057594152419328 (type LOB data). The off-row data node at page (1:915966), slot 0, text ID 1910439936 is referenced by page (1:914286), slot 0, but was not seen in
the scan.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:915969) allocated to object ID 1105439012, index ID 1, partition ID 72057594129612800, alloc unit ID 72057594152419328 (type LOB data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 1105439012, index ID 1, partition ID 72057594129612800, alloc unit ID 72057594152419328 (type LOB data). The off-row data node at page (1:915969), slot 0, text ID 1910439936 is referenced by page (1:914286), slot 0, but was not seen in
the scan.
Whats the best recommended practice to rectify these problems?. I would minimize the data loss as much as possible. I could use REPAIR_ALLOW_DATA_LOSS to repair but worried
about the dataloss. Trying to figure out any other better alternate approach available?.
I90Runner

There are so many good articles which talks about such issues at length.
I got this snapshot for you:
If any errors are reported by DBCC CHECKDB, we recommend restoring the database from the database backup instead of running REPAIR with one of the REPAIR options. If no backup exists, running repair corrects the errors reported. The repair option to use
is specified at the end of the list of reported errors. However, correcting the errors by using the REPAIR_ALLOW_DATA_LOSS option might require deleting some pages, and therefore some data.
Under some circumstances, values might be entered into the database that are not valid or out-of-range based on the data type of the column. DBCC CHECKDB can detect column values that are not valid for all column data types. Therefore, running DBCC
CHECKDB with the DATA_PURITY option on databases that have been upgraded from earlier versions of SQL Server might reveal preexisting column-value errors. Because SQL Server cannot automatically repair these errors, the column value must be manually updated.
If CHECKDB detects such an error, CHECKDB returns a warning, the error number 2570, and information to identify the affected row and manually correct the error.
The repair can be performed under a user transaction to let the user roll back the changes that were made. If repairs are rolled back, the database will still contain errors and must be restored from a backup. After repairs are completed, back up the database.
There is always some good practices to follow:
1. Maintain at-least two set of backup types.
2. Maintain never fail Backup Validation at Local DR and DR location for the backup you do for databases.
3. Maintain some Backup review process for all of these on daily\weekly\yearly basis.
4. Add job to do DBCC CheckDB on weekend at -least for you while adjusting with rebuild\upd stats job which might be already for you.
Now, if you have time to correct this issues, wherein you have made sure that this issue really exists then do following things:
1. Identify the objects which are marked as corrupted and check where DBCC is saying corrupted and why and make a note of that.
2. Take a backup of the database and restore on any dev\testing server and check these objects and whether you can restore with T-sql option like data from original table to temp table and drop\create table again. As mentioned above pointer may help you.
This way you will be able to recover database to a great extent which was stopping from helicopter snap of DBCC CheckDB.
Let me know, how it goes for you.
Santosh Singh

Errors in DB13 when running checkDB

Hello Experts,
When I run checkdb, it is giving the following error
BR0252W Function remove() failed for 'D:\oracle\BID\102\database\sap.ora' at location BrInitOraCreate-1
BR0253W errno 13: Permission denied
BR0976W Database message alert - level: WARNING, line: 568262, time: 2006-08-24 22.41.11, message:
Checkpoint not complete
Can anyone please advice on this issue.

Hi,
A late response, concerning LOG_BUFFER in Ora 10, but anyway
I believe that you are encountering Oracle Bug: 4930608. This is outlined in MetaLink Note: 351857.1 as follows:
Symptoms:
In customer environment, no matter what value is specified for the log_buffer, the buffer size remains at @14mbs
In 10G R2 Reference manual, it states that this parameter can no longer be modified and its set by default to 512K or 128K * the cpu count in the server. The document is in error.
Cause:
@From Bug 4592994....
In 10G R2, Oracle combines fixed SGA area and redo buffer [log buffer] together. If there is a free space after Oracle puts the combined buffers into a granule, that space is added to the redo buffer. Thus you see redo buffer has more space as expected. This is an expected behavior.
"In 10.2 the log buffer is rounded up to use the rest of the granule...
@ From bug 4930608... @ The granule size can be found from the hidden parameter @ #"_ksmg_granule_size" and in your case is probably 16Mb".
Solution:
Log_buffer can no longer be modified and will be set by default by Oracle.
Unfortunately a fix is not presently available, however you can remove the warning from dbcheck through transaction
regards Steven

ORA -01115 error in db13 checkdb

Hi expert ,
i am new to this fouram i have ora-01115 error in sap oracle 9i database ,
Please help me to solve the problem .
I am using ECC 5.0 ,win2k3 enterprise edition ,Oracle 9i
could anybody explain me what the relation of oracle block segment ,and windows block segment .
Could i solve the problem without reinstalling sap .
Please explain me in detail following paragraph ,which i read ,
 a corrupted database due the auto extended bug
 Corrupt block dba: 0x24024cd0 file=5. blocknum=150736.
 found during buffer read on disk type:0. ver.
 dba:0x00000000 inc:0x00000000 seq:0x00000000 incseq:0x00000000
 Entire contents of block is zero - block never written
 Reread of block=24024cd0 file=9. blocknum=150736. found same corupted Data
 Mishandled block information (in certain conditions), upon reading the database block, which indicates that a good block is corrupted. This is the bug in the Oracle version 8.1.x - 9.x, where the Oracle will raise the error:
ORA-600 [kcoapl_blkchk][ABN][RFN][INT CODE]
Pointing to failure condition during block check. This only happens when block checking is enabled.
 A problem with a faulty database trigger operation, causing data block corruptions
 ORA-01115: IO error reading block from file 6 (block # 14873)
 ORA-01110: data file 6: '/oracle/artist/artist01.dbf'
 ORA-27091: skgfqio: unable to queue I/O
 IBM AIX RISC System/6000 Error: 9: Bad file number
Thanx & Regards
RohitK

Hi experts ,
Regarding ORA 0600 ,the error which i found in db13 of 000,pls guide me in details as i am fresher basis consultant working in production enviorment.
I am pasting the check db log in db13 ,pls guide me if any problem is found.
Note that
1) i run sick tcode which shows no error report in the system .
2)I have configured stms ,
3)imported profiles from rz10 tcode from os level to sap level .
4)Created new client logged and doing local client copy but it cancelled every times .
In scc3 log it show different errors ,in sm21 log it show diffrerent errors .
It does not show ora 600 error anywhere in the logs ,but when i tried to check consistency of database through CHECKDB it show ora -600 error .
Hi experts pls tell me if required sm21 and and scc3 logs
CHECK DB LOG OF DB13
Detail log: cdwnjhor.chk
BR0801I BRCONNECT 6.40 (15)
BR0477I Oracle pfile D:\oracle\ora92\database\initDEV.ora created from spfile D:\oracle\ora92\database\spfileDEV.ora
BR0805I Start of BRCONNECT processing: cdwnjhor.chk 2007-11-05 11.16.25
BR0101I Parameters
Name Value
oracle_sid DEV
oracle_home D:\oracle\ora92
oracle_profile D:\oracle\ora92\database\initDEV.ora
sapdata_home D:\oracle\DEV
sap_profile D:\oracle\ora92\database\initDEV.sap
system_info SAPServiceDEV DSERVER Windows 5.2 Build 3790 Intel
oracle_info DEV 9.2.0.1.0 8192 630 3626441
sap_info 640 SAPDEV DEV TEMPLICENSE R3_ORA INITIAL
make_info NTintel OCI_920_SHARE Oct 12 2004
command_line brconnect -u / -c -f check
alert_log D:\oracle\DEV\saptrace\background\alert_dev.log
BR0280I BRCONNECT time stamp: 2007-11-05 11.17.25
BR0813I Schema owners found in database DEV: DBSNMP, OPS$DSERVER\DEVADM, OPS$DSERVER\SAPSERVICEDEV, OUTLN, SAPDEV*, SYS, SYSTEM
BR0118I Tablespaces and data files
Tablespace Status File Status Id. Size Device Type Link
PSAPDEV ONLINE+ D:\ORACLE\DEV\SAPDATA3\DEV_1\DEV.DATA1 ONLINE+ 3 2097160192 3 FILE NOLINK
PSAPDEV ONLINE+ D:\ORACLE\DEV\SAPDATA3\DEV_2\DEV.DATA2 ONLINE+ 4 2097160192 3 FILE NOLINK
PSAPDEV ONLINE+ D:\ORACLE\DEV\SAPDATA3\DEV_3\DEV.DATA3 ONLINE+ 5 2097160192 3 FILE NOLINK
PSAPDEV ONLINE+ D:\ORACLE\DEV\SAPDATA3\DEV_4\DEV.DATA4 ONLINE+ 6 2097160192 3 FILE NOLINK
PSAPDEV ONLINE+ D:\ORACLE\DEV\SAPDATA3\DEV_5\DEV.DATA5 ONLINE+ 7 2097160192 3 FILE NOLINK
PSAPDEV ONLINE+ D:\ORACLE\DEV\SAPDATA4\DEV_10\DEV.DATA10 ONLINE+ 12 2097160192 3 FILE NOLINK
PSAPDEV ONLINE+ D:\ORACLE\DEV\SAPDATA4\DEV_11\DEV.DATA11 ONLINE+ 27 2097160192 3 FILE NOLINK
PSAPDEV ONLINE+ D:\ORACLE\DEV\SAPDATA4\DEV_12\DEV.DATA12 ONLINE+ 28 2097160192 3 FILE NOLINK
PSAPDEV ONLINE+ D:\ORACLE\DEV\SAPDATA4\DEV_13\DEV.DATA13 ONLINE+ 29 2097160192 3 FILE NOLINK
PSAPDEV ONLINE+ D:\ORACLE\DEV\SAPDATA4\DEV_14\DEV.DATA14 ONLINE+ 30 2097160192 3 FILE NOLINK
PSAPDEV ONLINE+ D:\ORACLE\DEV\SAPDATA4\DEV_6\DEV.DATA6 ONLINE+ 8 2097160192 3 FILE NOLINK
PSAPDEV ONLINE+ D:\ORACLE\DEV\SAPDATA4\DEV_7\DEV.DATA7 ONLINE+ 9 2097160192 3 FILE NOLINK
PSAPDEV ONLINE+ D:\ORACLE\DEV\SAPDATA4\DEV_8\DEV.DATA8 ONLINE+ 10 2097160192 3 FILE NOLINK
PSAPDEV ONLINE+ D:\ORACLE\DEV\SAPDATA4\DEV_9\DEV.DATA9 ONLINE+ 11 2097160192 3 FILE NOLINK
PSAPDEV640 ONLINE+ D:\ORACLE\DEV\SAPDATA1\DEV640_1\DEV640.DATA1 ONLINE+ 13 2097160192 3 FILE NOLINK
PSAPDEV640 ONLINE+ D:\ORACLE\DEV\SAPDATA1\DEV640_2\DEV640.DATA2 ONLINE+ 14 2097160192 3 FILE NOLINK
PSAPDEV640 ONLINE+ D:\ORACLE\DEV\SAPDATA1\DEV640_3\DEV640.DATA3 ONLINE+ 15 2097160192 3 FILE NOLINK
PSAPDEV640 ONLINE+ D:\ORACLE\DEV\SAPDATA1\DEV640_4\DEV640.DATA4 ONLINE+ 16 2097160192 3 FILE NOLINK
PSAPDEV640 ONLINE+ D:\ORACLE\DEV\SAPDATA1\DEV640_5\DEV640.DATA5 ONLINE+ 17 2097160192 3 FILE NOLINK
PSAPDEV640 ONLINE+ D:\ORACLE\DEV\SAPDATA2\DEV640_10\DEV640.DATA10 ONLINE+ 22 2097160192 3 FILE NOLINK
PSAPDEV640 ONLINE+ D:\ORACLE\DEV\SAPDATA2\DEV640_6\DEV640.DATA6 ONLINE+ 18 2097160192 3 FILE NOLINK
PSAPDEV640 ONLINE+ D:\ORACLE\DEV\SAPDATA2\DEV640_7\DEV640.DATA7 ONLINE+ 19 2097160192 3 FILE NOLINK
PSAPDEV640 ONLINE+ D:\ORACLE\DEV\SAPDATA2\DEV640_8\DEV640.DATA8 ONLINE+ 20 2097160192 3 FILE NOLINK
PSAPDEV640 ONLINE+ D:\ORACLE\DEV\SAPDATA2\DEV640_9\DEV640.DATA9 ONLINE+ 21 2097160192 3 FILE NOLINK
PSAPDEV640 ONLINE+ D:\ORACLE\DEV\SAPDATA3\DEV640_11\DEV640.DATA11 ONLINE+ 23 2097160192 3 FILE NOLINK
PSAPDEV640 ONLINE+ D:\ORACLE\DEV\SAPDATA4\DEV640_12\DEV640.DATA12 ONLINE+ 24 2097160192 3 FILE NOLINK
PSAPDEV640 ONLINE+ D:\ORACLE\DEV\SAPDATA4\DEV640_13\DEV640.DATA13 ONLINE+ 25 2097160192 3 FILE NOLINK
PSAPDEV640 ONLINE+ D:\ORACLE\DEV\SAPDATA4\DEV640_14\DEV640.DATA14 ONLINE+ 31 2097160192 3 FILE NOLINK
PSAPDEV640 ONLINE+ D:\ORACLE\DEV\SAPDATA4\DEV640_15\DEV640.DATA15 ONLINE+ 32 2097160192 3 FILE NOLINK
PSAPDEV640 ONLINE+ D:\ORACLE\DEV\SAPDATA4\DEV640_16\DEV640.DATA16 ONLINE+ 33 2097160192 3 FILE NOLINK
PSAPDEV640 ONLINE+ D:\ORACLE\DEV\SAPDATA4\DEV640_17\DEV640.DATA17 ONLINE+ 34 2097160192 3 FILE NOLINK
PSAPDEVUSR ONLINE+ D:\ORACLE\DEV\SAPDATA4\DEVUSR_1\DEVUSR.DATA1 ONLINE+ 26 20979712 3 FILE NOLINK
PSAPTEMP ONLINE# D:\ORACLE\DEV\SAPDATA1\TEMP_1\TEMP.DATA1 ONLINE+ -1 702554112 3 FILE NOLINK
PSAPUNDO ONLINE- D:\ORACLE\DEV\SAPDATA1\UNDO_1\UNDO.DATA1 ONLINE+ 2 2915049472 3 FILE NOLINK
PSAPUNDO ONLINE- D:\ORACLE\DEV\SAPDATA1\UNDO_2\UNDO.DATA2 ONLINE 39 2915049472 3 FILE NOLINK
PSAPUNDO ONLINE- D:\ORACLE\DEV\SAPDATA1\UNDO_3\UNDO.DATA3 ONLINE 40 2915049472 3 FILE NOLINK
PSAPUNDO ONLINE- D:\ORACLE\DEV\SAPDATA1\UNDO_4\UNDO.DATA4 ONLINE 41 2915049472 3 FILE NOLINK
PSAPUNDO ONLINE- D:\ORACLE\DEV\SAPDATA1\UNDO_5\UNDO.DATA5 ONLINE 42 2915049472 3 FILE NOLINK
SYSTEM ONLINE+ D:\ORACLE\DEV\SAPDATA1\SYSTEM_1\SYSTEM.DATA1 SYSTEM+ 1 555753472 3 FILE NOLINK
SYSTEM ONLINE+ D:\ORACLE\DEV\SAPDATA1\SYSTEM_2\SYSTEM.DATA2 SYSTEM+ 35 555753472 3 FILE NOLINK
SYSTEM ONLINE+ D:\ORACLE\DEV\SAPDATA1\SYSTEM_3\SYSTEM.DATA3 SYSTEM+ 36 555753472 3 FILE NOLINK
SYSTEM ONLINE+ D:\ORACLE\DEV\SAPDATA1\SYSTEM_4\SYSTEM.DATA4 SYSTEM+ 37 555753472 3 FILE NOLINK
SYSTEM ONLINE+ D:\ORACLE\DEV\SAPDATA1\SYSTEM_5\SYSTEM.DATA5 SYSTEM+ 38 555753472 3 FILE NOLINK
BR0119I Redo log files
File Status Group Size Device Type Link
D:\ORACLE\DEV\ORIGLOGA\LOG_G11M1.DBF INUSE 1 52429312 3 FILE NOLINK
D:\ORACLE\DEV\MIRRLOGA\LOG_G11M2.DBF INUSE 1 52429312 3 FILE NOLINK
D:\ORACLE\DEV\ORIGLOGB\LOG_G12M1.DBF INUSE 2 52429312 3 FILE NOLINK
D:\ORACLE\DEV\MIRRLOGB\LOG_G12M2.DBF INUSE 2 52429312 3 FILE NOLINK
D:\ORACLE\DEV\ORIGLOGA\LOG_G13M1.DBF INUSE 3 52429312 3 FILE NOLINK
D:\ORACLE\DEV\MIRRLOGA\LOG_G13M2.DBF INUSE 3 52429312 3 FILE NOLINK
D:\ORACLE\DEV\ORIGLOGB\LOG_G14M1.DBF INUSE 4 52429312 3 FILE NOLINK
D:\ORACLE\DEV\MIRRLOGB\LOG_G14M2.DBF INUSE 4 52429312 3 FILE NOLINK
BR0120I Control files
File Size Device Type Link
D:\ORACLE\DEV\ORIGLOGA\CNTRL\CNTRLDEV.DBF 6791168 3 FILE NOLINK
D:\ORACLE\DEV\SAPDATA1\SYSTEM_1\CNTRL\CNTRLDEV.DBF 6791168 3 FILE NOLINK
D:\ORACLE\DEV\SAPARCH\CNTRL\CNTRLDEV.DBF 6791168 3 FILE NOLINK
BR0982I Database disk volumes
Directory / Raw disk Device Total[KB] Free[KB] Used[%]
D:\oracle\ora92 3 204804620 119569600 41.62
D:\oracle\DEV 3 204804620 119569600 41.62
D:\ORACLE\DEV\MIRRLOGA 3 204804620 119569600 41.62
D:\ORACLE\DEV\MIRRLOGB 3 204804620 119569600 41.62
D:\ORACLE\DEV\ORIGLOGA 3 204804620 119569600 41.62
D:\ORACLE\DEV\ORIGLOGB 3 204804620 119569600 41.62
D:\ORACLE\DEV\SAPARCH 3 204804620 119569600 41.62
D:\ORACLE\DEV\SAPDATA1 3 204804620 119569600 41.62
D:\ORACLE\DEV\SAPDATA1\SYSTEM_1\CNTRL 3 204804620 119569600 41.62
D:\ORACLE\DEV\SAPDATA2 3 204804620 119569600 41.62
D:\ORACLE\DEV\SAPDATA3 3 204804620 119569600 41.62
D:\ORACLE\DEV\SAPDATA4 3 204804620 119569600 41.62
D:\oracle\DEV\saparch 3 204804620 119569592 41.62
D:\oracle\DEV\sapbackup 3 204804620 119569592 41.62
D:\oracle\DEV\sapcheck 3 204804620 119569592 41.62
D:\oracle\DEV\sapreorg 3 204804620 119569592 41.62
D:\oracle\DEV\saptrace 3 204804620 119569592 41.62
BR0280I BRCONNECT time stamp: 2007-11-05 11.17.42
BR0814I Number of tables in schema of owner SAPDEV: 43103
BR0836I Number of info cube tables found for owner SAPDEV: 49
BR0814I Number of tables in schema of owner SYS: 292
BR0814I Number of tables/partitions in schema of owner SYSTEM: 128/27
BR0280I BRCONNECT time stamp: 2007-11-05 11.17.53
BR0815I Number of indexes in schema of owner SAPDEV: 51463
BR0815I Number of indexes in schema of owner SYS: 289
BR0815I Number of indexes/partitions in schema of owner SYSTEM: 157/24
BR0280I BRCONNECT time stamp: 2007-11-05 11.23.18
BR0816I Number of segments in schema of owner OPS$DSERVER\DEVADM: 1
BR0816I Number of segments in schema of owner OUTLN: 6
BR0816I Number of segments/LOBs in schema of owner SAPDEV: 95252/343
BR0816I Number of segments/LOBs in schema of owner SYS: 645/22
BR0816I Number of segments/LOBs in schema of owner SYSTEM: 327/21
BR0983I Tablespace fragmentation
Tablespace Files Tables Indexes Extents Total[KB] Used[%] Free[KB] Extents MaxSize[KB] Used[%] Free[KB] Largest[KB]
PSAPDEV 14 42821 51075 111312 28672000 66.98 9466880 7 143360000+ 13.40+ 124154880+ 8192000:8192000:8192000:8192000:8192000+
PSAPDEV640 17 273 378 8401 34816000 70.91 10128448 13 154378240+ 15.99+ 129690688+ 8192000:8192000:8192000:8192000:8192000+
PSAPDEVUSR 1 9 10 19 20480 6.25 19200 1 10240000+ 0.01+ 10238720+ 10219520+:19200:0:0:0
PSAPTEMP 1 0 0 1 686080 36.72 434176 1 10240000+ 2.46+ 9988096+ 9553920+:434176:0:0:0
PSAPUNDO 5 0 0 1066 14233600 20.49 11316928 5 21626880+ 13.49+ 18710208+ 7393280+:2846656:2846656:2830272:2781120
SYSTEM 5 393 422 2107 2713600 19.95 2172352 5 51200000+ 1.06+ 50658752+ 9697280:9697280:9697280:9697280:9697280+
Total: 43 43496 51885 122906 81141760 58.67 33537984 32 391045120 12.17 343441344 53248000:29381312:28927936:28911552:28862400
BR0280I BRCONNECT time stamp: 2007-11-05 11.23.18
BR0818I Number of tables found in DBDIFF for owner SAPDEV: 2
BR0280I BRCONNECT time stamp: 2007-11-05 11.23.19
BR0818I Number of tables found in DBSTATC for owner SAPDEV: 403
BR0280I BRCONNECT time stamp: 2007-11-05 11.23.26
BR0819I Number of pool and cluster tables found in DDNTT for owner SAPDEV: 169
BR0280I BRCONNECT time stamp: 2007-11-05 11.23.26
BR0961I Number of conditions found in DBCHECKORA: 70
BR0962I Check conditions for database administration:
Pos. Act. Lev. Condition Object
Description
1 Y W ARCHIVER_STUCK
Out of space in archive directory - more than 90% space used
2 Y E CONTROL_FILE_MIRROR
Control file not mirrored
3 Y E CONTROL_FILE_MISSING
Control file missing on disk
4 Y W CRITICAL_FILE
File autoextend can cause file system overflow
5 Y W CRITICAL_SEGMENT
Segment can cause tablespace overflow - by allocating up to 2 next extent(s)
6 Y E DATA_FILE_MISMATCH
Data file marked as missing in control file
7 Y E DATA_FILE_MISSING
Data file missing on disk
8 Y E FILE_OFFLINE
Database file offline
9 Y W FILE_SYSTEM_FULL
File system full - more than 99% space used
10 Y E HARMFUL_STATISTICS
Table or index has harmful optimizer statistics
11 Y E INVALID_FILE_TYPE
Invalid operating system file type
12 Y W IN_WRONG_TABLESPACE
Table or index in wrong tablespace
13 Y E MISSING_INDEX
Table has no index
14 Y E MISSING_STATISTICS
Table or index has no optimizer statistics
15 Y E NOARCHIVELOG_MODE
Database in NOARCHIVELOG mode
16 Y W PCTINCREASE_NOT_ZERO
PCTINCREASE value not equal zero
17 Y E REDOLOG_FILE_MIRROR
Redo log file not mirrored
18 Y E REDOLOG_FILE_MISSING
Redo log file missing on disk
19 Y W TABLESPACE_FULL
Tablespace full - more than 95% space used
20 Y W TABLESPACE_IN_BACKUP
Tablespace in backup mode
21 Y E TABLESPACE_OFFLINE
Tablespace offline
22 Y W TOO_MANY_EXTENTS
Segment has too many extents - more than 90% of MAXEXTENTS used
BR0963I Check conditions for database operations:
Pos. Act. Lev. Condition Description
1 Y W ARCHIVE_TOO_OLD Last successful archive log backup older than 10 days (or has not been run)
2 Y W BACKUP_TOO_OLD Last successful complete database backup older than 10 days (or has not been run)
3 Y W LAST_ARCHIVE_FAILED Last archive log backup failed
4 Y W LAST_BACKUP_FAILED Last complete database backup failed
5 Y W LAST_OPERATION_FAILED Last 'chk' operation failed
6 N W LAST_OPERATION_FAILED Last DBA operation failed
7 Y W LAST_STATS_FAILED Last update optimizer statistics failed
8 Y W OPERATION_TOO_OLD Last successful 'chk' operation older than 10 days (or has not been run)
9 N W OPERATION_TOO_OLD Last successful DBA operation older than 10 days (or has not been run)
10 Y W STATS_TOO_OLD Last successful update optimizer statistics older than 10 days (or has not been run)
BR0964I Check conditions for database messages:
Pos. Act. Lev. Message Description
1 Y W ORA-00060 Deadlock while waiting for resource
2 Y E ORA-00272 Error writing archive log
3 Y E ORA-00376 Database file cannot be read
4 Y E ORA-00600 Oracle internal error
5 Y E ORA-01113 Data file needs media recovery
6 Y E ORA-01114 I/O error writing database file
7 Y E ORA-01115 I/O error reading database file
8 Y E ORA-01122 File verification check failed
9 Y E ORA-01135 Database file is offline
10 Y W ORA-01149 Cannot shutdown - data file in backup mode
11 Y W ORA-01555 Snapshot too old
12 Y W ORA-01562 Failed to extend rollback segment
13 Y E ORA-01578 Database block corrupted
14 Y E ORA-03113 End-of-file on communication channel
15 Y E ORA-07445 Exception encountered: core dump
16 Y W Checkpoint not complete
BR0965I Check conditions for database profile:
Pos. Act. Lev. Parameter Condition Value Unit
1 Y W CONTROL_FILE_RECORD_KEEP_TIME < 30
2 Y W CURSOR_SPACE_FOR_TIME <> FALSE
3 Y W DBWR_IO_SLAVES <> 0
4 Y W DB_BLOCK_BUFFERS <> 0
5 Y E DB_BLOCK_SIZE <> 8192
6 Y W DB_FILES < 254
7 Y W DB_FILE_MULTIBLOCK_READ_COUNT > 32
8 Y W DISK_ASYNCH_IO <> TRUE
9 Y W HASH_JOIN_ENABLED <> FALSE
10 Y E LOG_ARCHIVE_START <> TRUE
11 Y W LOG_BUFFER >< 2048,512 K
12 Y W LOG_CHECKPOINT_INTERVAL <> 0
13 Y W LOG_CHECKPOINT_TIMEOUT <> 0
14 Y W OPEN_CURSORS >< 2000,800
15 Y W OPTIMIZER_FEATURES_ENABLE <> 9.2.0
16 Y W OPTIMIZER_INDEX_COST_ADJ <> 10
17 Y W OPTIMIZER_MODE <> CHOOSE
18 Y W SHARED_POOL_SIZE < 50 M
19 Y E SORT_AREA_RETAINED_SIZE > 0
20 Y E SORT_AREA_SIZE >< 4,2 M
21 Y E TIMED_STATISTICS <> TRUE
22 Y E TRANSACTION_AUDITING <> FALSE
BR0280I BRCONNECT time stamp: 2007-11-05 11.23.26
BR0807I Name of database instance: DEV
BR0808I BRCONNECT action ID: cdwnjhor
BR0809I BRCONNECT function ID: chk
BR0810I BRCONNECT function: check
BR0951I Number of active/inactive check conditions for database administration: 22/0
BR0952I Number of active/inactive check conditions for database operations: 8/2
BR0953I Number of active/inactive check conditions for database messages: 16/0
BR0954I Number of active/inactive check conditions for database profile: 22/0
BR0960I Last successful BRCONNECT check run: caaaaaaa.chk 0000-00-00 00.00.00
BR0126I Unattended mode active - no operator confirmation required
BR0280I BRCONNECT time stamp: 2007-11-05 11.23.26
BR0969I Checking database administration...
BR0280I BRCONNECT time stamp: 2007-11-05 11.23.26
BR0972I Checking database operations...
BR0973W Database operation alert - level: WARNING, operation: Archive log backup, condition: Operation too old or has not been run in clean-up period
BR0973W Database operation alert - level: WARNING, operation: Complete database backup, condition: Operation too old or has not been run in clean-up period
BR0973W Database operation alert - level: WARNING, operation: chk, condition: Operation too old or has not been run in clean-up period
BR0280I BRCONNECT time stamp: 2007-11-05 11.23.27
BR0974I Checking database messages...
BR0976W Database message alert - level: ERROR, line: 468, time: 2030-11-04 10.13.17, message:
ORA-00600: internal error code, arguments: [4406], [0x6A366AA0], [0x0], [], [], [], [], []
BR0976W Database message alert - level: ERROR, line: 472, time: 2030-11-04 10.13.17, message:
ORA-00600: internal error code, arguments: [kcbklbc_4], [], [], [], [], [], [], []
BR0976W Database message alert - level: ERROR, line: 478, time: 2030-11-04 10.13.20, message:
ORA-00600: internal error code, arguments: [KSSRMP1], [], [], [], [], [], [], []
BR0976W Database message alert - level: ERROR, line: 479, time: 2030-11-04 10.13.20, message:
ORA-00600: internal error code, arguments: [kcbklbc_4], [], [], [], [], [], [], []
BR0976W Database message alert - level: ERROR, line: 483, time: 2030-11-04 10.13.22, message:
ORA-00600: internal error code, arguments: [KSSRMP1], [], [], [], [], [], [], []
BR0976W Database message alert - level: ERROR, line: 484, time: 2030-11-04 10.13.22, message:
ORA-00600: internal error code, arguments: [KSSRMP1], [], [], [], [], [], [], []
BR0976W Database message alert - level: ERROR, line: 485, time: 2030-11-04 10.13.22, message:
ORA-00600: internal error code, arguments: [kcbklbc_4], [], [], [], [], [], [], []
BR0976W Database message alert - level: ERROR, line: 499, time: 2030-11-04 10.13.26, message:
ORA-00600: internal error code, arguments: [kcbgcur_9], [8388713], [29], [1610612736], [1610612738], [], [], []
BR0976W Database message alert - level: ERROR, line: 504, time: 2030-11-04 10.13.28, message:
ORA-00600: internal error code, arguments: [kcbgcur_9], [8388713], [29], [1610612736], [1610612738], [], [], []
BR0976W Database message alert - level: ERROR, line: 510, time: 2030-11-04 10.13.30, message:
ORA-00600: internal error code, arguments: [4406], [0x6A366AA0], [0x0], [], [], [], [], []
BR0976W Database message alert - level: ERROR, line: 514, time: 2030-11-04 10.13.31, message:
ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], []
BR0976W Database message alert - level: ERROR, line: 521, time: 2030-11-04 10.13.31, message:
ORA-00600: internal error code, arguments: [kcbgcur_9], [8388713], [29], [1610612736], [1610612738], [], [], []
BR0280I BRCONNECT time stamp: 2007-11-05 11.23.27
BR0977I Checking database profile...
BR0979I Changes in database profile parameters:
Pos. Parameter name Old value
 New value
1 O7_DICTIONARY_ACCESSIBILITY (new)
 FALSE
2 AQ_TM_PROCESSES (new)
 0
3 ARCHIVE_LAG_TARGET (new)
 0
4 AUDIT_SYS_OPERATIONS (new)
 FALSE
5 AUDIT_TRAIL (new)
 NONE
6 BACKGROUND_CORE_DUMP (new)
 partial
7 BACKGROUND_DUMP_DEST (new)
 D:\oracle\DEV\saptrace\background
8 BACKUP_TAPE_IO_SLAVES (new)
 FALSE
9 BITMAP_MERGE_AREA_SIZE (new)
 1048576
10 BLANK_TRIMMING (new)
 FALSE
11 CIRCUITS (new)
 0
12 CLUSTER_DATABASE (new)
 FALSE
13 CLUSTER_DATABASE_INSTANCES (new)
 1
14 COMMIT_POINT_STRENGTH (new)
 1
15 COMPATIBLE (new)
 9.2.0
16 CONTROL_FILE_RECORD_KEEP_TIME (new)
 30
17 CONTROL_FILES (new)
 D:\oracle\DEV\origlogA\cntrl\cntrlDEV.dbf, D:\oracle\DEV\sapdata1\system_1\cntrl\cntrlDEV.dbf, D:\oracle\DEV\saparch\cntrl\cntrlDEV.dbf
18 CORE_DUMP_DEST (new)
 D:\oracle\DEV\saptrace\background
19 CPU_COUNT (new)
 1
20 CREATE_BITMAP_AREA_SIZE (new)
 8388608
21 CURSOR_SHARING (new)
 EXACT
22 CURSOR_SPACE_FOR_TIME (new)
 FALSE
23 DB_16K_CACHE_SIZE (new)
 0
24 DB_2K_CACHE_SIZE (new)
 0
25 DB_32K_CACHE_SIZE (new)
 0
26 DB_4K_CACHE_SIZE (new)
 0
27 DB_8K_CACHE_SIZE (new)
 0
28 DB_BLOCK_BUFFERS (new)
 0
29 DB_BLOCK_CHECKING (new)
 FALSE
30 DB_BLOCK_CHECKSUM (new)
 TRUE
31 DB_BLOCK_SIZE (new)
 8192
32 DB_CACHE_ADVICE (new)
 ON
33 DB_CACHE_SIZE (new)
 83886080
34 DB_FILE_MULTIBLOCK_READ_COUNT (new)
 8
35 DB_FILES (new)
 254
36 DB_KEEP_CACHE_SIZE (new)
 0
37 DB_NAME (new)
 DEV
38 DB_RECYCLE_CACHE_SIZE (new)
 0
39 DB_WRITER_PROCESSES (new)
 1
40 DBLINK_ENCRYPT_LOGIN (new)
 FALSE
41 DBWR_IO_SLAVES (new)
 0
42 DG_BROKER_CONFIG_FILE1 (new)
 %ORACLE_HOME%\DATABASE\DR1%ORACLE_SID%.DAT
43 DG_BROKER_CONFIG_FILE2 (new)
 %ORACLE_HOME%\DATABASE\DR2%ORACLE_SID%.DAT
44 DG_BROKER_START (new)
 FALSE
45 DISK_ASYNCH_IO (new)
 TRUE
46 DISTRIBUTED_LOCK_TIMEOUT (new)
 60
47 DML_LOCKS (new)
 4000
48 DRS_START (new)
 FALSE
49 ENQUEUE_RESOURCES (new)
 8000
50 FAST_START_IO_TARGET (new)
 0
51 FAST_START_MTTR_TARGET (new)
 900
52 FAST_START_PARALLEL_ROLLBACK (new)
 LOW
53 FILE_MAPPING (new)
 FALSE
54 GLOBAL_NAMES (new)
 FALSE
55 HASH_AREA_SIZE (new)
 4194304
56 HASH_JOIN_ENABLED (new)
 FALSE
57 HI_SHARED_MEMORY_ADDRESS (new)
 0
58 HS_AUTOREGISTER (new)
 TRUE
59 INSTANCE_NAME (new)
 dev
60 INSTANCE_NUMBER (new)
 0
61 JAVA_MAX_SESSIONSPACE_SIZE (new)
 0
62 JAVA_POOL_SIZE (new)
 25165824
63 JAVA_SOFT_SESSIONSPACE_LIMIT (new)
 0
64 JOB_QUEUE_PROCESSES (new)
 0
65 LARGE_POOL_SIZE (new)
 0
66 LICENSE_MAX_SESSIONS (new)
 0
67 LICENSE_MAX_USERS (new)
 0
68 LICENSE_SESSIONS_WARNING (new)
 0
69 LOCK_SGA (new)
 FALSE
70 LOG_ARCHIVE_DEST (new)
 D:\oracle\DEV\oraarch\DEVarch
71 LOG_ARCHIVE_DEST_STATE_1 (new)
 enable
72 LOG_ARCHIVE_DEST_STATE_10 (new)
 enable
73 LOG_ARCHIVE_DEST_STATE_2 (new)
 enable
74 LOG_ARCHIVE_DEST_STATE_3 (new)
 enable
75 LOG_ARCHIVE_DEST_STATE_4 (new)
 enable
76 LOG_ARCHIVE_DEST_STATE_5 (new)
 enable
77 LOG_ARCHIVE_DEST_STATE_6 (new)
 enable
78 LOG_ARCHIVE_DEST_STATE_7 (new)
 enable
79 LOG_ARCHIVE_DEST_STATE_8 (new)
 enable
80 LOG_ARCHIVE_DEST_STATE_9 (new)
 enable
81 LOG_ARCHIVE_FORMAT (new)
 ARC%S.%T
82 LOG_ARCHIVE_MAX_PROCESSES (new)
 2
83 LOG_ARCHIVE_MIN_SUCCEED_DEST (new)
 1
84 LOG_ARCHIVE_START (new)
 TRUE
85 LOG_ARCHIVE_TRACE (new)
 0
86 LOG_BUFFER (new)
 1048576
87 LOG_CHECKPOINT_INTERVAL (new)
 0
88 LOG_CHECKPOINT_TIMEOUT (new)
 0
89 LOG_CHECKPOINTS_TO_ALERT (new)
 TRUE
90 LOG_PARALLELISM (new)
 1
91 LOGMNR_MAX_PERSISTENT_SESSIONS (new)
 1
92 MAX_COMMIT_PROPAGATION_DELAY (new)
 700
93 MAX_DISPATCHERS (new)
 5
94 MAX_DUMP_FILE_SIZE (new)
 UNLIMITED
95 MAX_ENABLED_ROLES (new)
 30
96 MAX_ROLLBACK_SEGMENTS (new)
 30
97 MAX_SHARED_SERVERS (new)
 20
98 MTS_CIRCUITS (new)
 0
99 MTS_MAX_DISPATCHERS (new)
 5
100 MTS_MAX_SERVERS (new)
 20
101 MTS_MULTIPLE_LISTENERS (new)
 FALSE
102 MTS_SERVERS (new)
 0
103 MTS_SERVICE (new)
 DEV
104 MTS_SESSIONS (new)
 0
105 NLS_LANGUAGE (new)
 AMERICAN
106 NLS_LENGTH_SEMANTICS (new)
 BYTE
107 NLS_NCHAR_CONV_EXCP (new)
 FALSE
108 NLS_TERRITORY (new)
 AMERICA
109 OBJECT_CACHE_MAX_SIZE_PERCENT (new)
 10
110 OBJECT_CACHE_OPTIMAL_SIZE (new)
 102400
111 OLAP_PAGE_POOL_SIZE (new)
 33554432
112 OPEN_CURSORS (new)
 800
113 OPEN_LINKS (new)
 4
114 OPEN_LINKS_PER_INSTANCE (new)
 4
115 OPTIMIZER_DYNAMIC_SAMPLING (new)
 1
116 OPTIMIZER_FEATURES_ENABLE (new)
 9.2.0
117 OPTIMIZER_INDEX_CACHING (new)
 0
118 OPTIMIZER_INDEX_COST_ADJ (new)
 10
119 OPTIMIZER_MAX_PERMUTATIONS (new)
 2000
120 OPTIMIZER_MODE (new)
 CHOOSE
121 ORACLE_TRACE_COLLECTION_PATH (new)
 %ORACLE_HOME%\OTRACE\ADMIN\CDF\
122 ORACLE_TRACE_COLLECTION_SIZE (new)
 5242880
123 ORACLE_TRACE_ENABLE (new)
 FALSE
124 ORACLE_TRACE_FACILITY_NAME (new)
 oracled
125 ORACLE_TRACE_FACILITY_PATH (new)
 %ORACLE_HOME%\OTRACE\ADMIN\FDF\
126 OS_AUTHENT_PREFIX (new)
 OPS$
127 OS_ROLES (new)
 FALSE
128 PARALLEL_ADAPTIVE_MULTI_USER (new)
 FALSE
129 PARALLEL_AUTOMATIC_TUNING (new)
 FALSE
130 PARALLEL_EXECUTION_MESSAGE_SIZE (new)
 2148
131 PARALLEL_MAX_SERVERS (new)
 5
132 PARALLEL_MIN_PERCENT (new)
 0
133 PARALLEL_MIN_SERVERS (new)
 0
134 PARALLEL_SERVER (new)
 FALSE
135 PARALLEL_SERVER_INSTANCES (new)
 1
136 PARALLEL_THREADS_PER_CPU (new)
 2
137 PARTITION_VIEW_ENABLED (new)
 FALSE
138 PGA_AGGREGATE_TARGET (new)
 85144371
139 PLSQL_COMPILER_FLAGS (new)
 INTERPRETED
140 PLSQL_NATIVE_LIBRARY_SUBDIR_COUNT (new)
 0
141 PLSQL_V2_COMPATIBILITY (new)
 FALSE
142 PRE_PAGE_SGA (new)
 FALSE
143 PROCESSES (new)
 80
144 QUERY_REWRITE_ENABLED (new)
 false
145 QUERY_REWRITE_INTEGRITY (new)
 enforced
146 READ_ONLY_OPEN_DELAYED (new)
 FALSE
147 RECOVERY_PARALLELISM (new)
 0
148 REMOTE_ARCHIVE_ENABLE (new)
 true
149 REMOTE_DEPENDENCIES_MODE (new)
 TIMESTAMP
150 REMOTE_LOGIN_PASSWORDFILE (new)
 NONE
151 REMOTE_OS_AUTHENT (new)
 TRUE
152 REMOTE_OS_ROLES (new)
 FALSE
153 REPLICATION_DEPENDENCY_TRACKING (new)
 TRUE
154 RESOURCE_LIMIT (new)
 FALSE
155 ROW_LOCKING (new)
 always
156 SERIAL_REUSE (new)
 DISABLE
157 SERIALIZABLE (new)
 FALSE
158 SERVICE_NAMES (new)
 DEV
159 SESSION_CACHED_CURSORS (new)
 0
160 SESSION_MAX_OPEN_FILES (new)
 10
161 SESSIONS (new)
 96
162 SGA_MAX_SIZE (new)
 219749116
163 SHADOW_CORE_DUMP (new)
 partial
164 SHARED_MEMORY_ADDRESS (new)
 0
165 SHARED_POOL_RESERVED_SIZE (new)
 9011200
166 SHARED_POOL_SIZE

Error during CHECKDB

Hi Team,
I am getting an error message when i peform CHECKDB by scheduling a job in DB13. When i run the command line from AIX server it seems to go fine.
The error message is
Job started
Step 001 started (program RSDBAJOB, variant &0000000000236, user ID RAVISSHA)
Execute logical command BRCONNECT On host ssaptdb
Parameters: -u /-c -f check
BR0801I BRCONNECT 6.40 (15)
BR0805I Start of BRCONNECT processing: cdxgcmiq.chk 2008-02-12 08.18.40
BR0280I BRCONNECT time stamp: 2008-02-12 08.18.42
BR0301E SQL error -1017 at location db_connect-2
ORA-01017: invalid username/password; logon denied
BR0310E Connect to database instance BWI failed
BR0280I BRCONNECT time stamp: 2008-02-12 08.18.42
BR0301E SQL error -1017 at location db_connect-2
ORA-01017: invalid username/password; logon denied
BR0310E Connect to database instance BWI failed
BR0806I End of BRCONNECT processing: cdxgcmiq.chk2008-02-12 08.18.42
BR0280I BRCONNECT time stamp: 2008-02-12 08.18.42
BR0804I BRCONNECT terminated with errors
External program terminated with exit code 3
BRCONNECT returned error status E
Job finished
Could somebody please help???

Hi,
I am getting the below error message when trying to create the User.
I also wanted to mention that this system was working for long and i have other jobs like Update jobs and backup's working fine
ssaptdb:orabwi:/home/orabwi > sqlplus /nolog
SQLPlus: Release 9.2.0.8.0 - Production on Tue Feb 12 09:27:46 2008*
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
SQL> conn /as sysdba
Connected.
SQL> create user ops$orabwi identified externally;
create user ops$orabwi identified externally
ERROR at line 1:
ORA-01920: user name 'OPS$ORABWI' conflicts with another user or role name
Kindly help.

Error in CHECKDB

Hi,
I am getting an error message when i peform CHECKDB by scheduling a job in DB13. The error message is:
Job started
Step 001 started (program RSDBAJOB, variant &0000000000112, user name DDIC)
Execute logical command BRCONNECT On host sapda31
Parameters: -u / -c -f check
BR801I BRCONNECT 6.20 (133)
BR805I Start of BRCONNECT processing: cdxjvnao.chk 2008-03-03 03.00.58
BR280I Time stamp 2008-03-03 03.01.05
BR301E SQL error -27140 at location db_connect-2
ORA-27140: attach to post/wait facility failed
BR310E Connect to database instance A31 failed
BR280I Time stamp 2008-03-03 03.01.05
BR301E SQL error -27140 at location thr_db_connect-4
ORA-27140: attach to post/wait facility failed
BR310E Connect to database instance A31 failed
BR806I End of BRCONNECT processing: cdxjvnao.chk 2008-03-03 03.01.05
BR280I Time stamp 2008-03-03 03.01.05
BR804I BRCONNECT terminated with errors
External program terminated with exit code 3
BRCONNECT returned error status E
Job finished
The database is running in Oracle9i.
Please suggest how to solve this issue..

Hi,
The error ora-27140 is due to the lack accessibility to oracle
executables.
1. Please make sure that all oracle executables has permission as per
the note mentioned below.
583861 UNIX: Errors due to Oracle executable
(chmod 6751 oracle) Owner ORA<SID>
2. If the problem is not solved with this, please download the latest
patch level of the BR*tools as per SAP note 12741.
" Check the owner, the group and the permissions for sapdba and the br*
tools as described in Note 113747.
regards,
kaushal

DB13 CheckDB Error

Hi Experts,
While running Checkdb through DB13 , I am getting below error :-
BR0301E SQL error -1031 at location BrDbcheckoraRead-1, SQL statement:
'OPEN curs_91 CURSOR FOR'
'SELECT NVL(UPPER(TYPE), ' '), NVL(UPPER(PARAM), ' '), NVL(PARAM, ' '), NVL(OBJECT, ' '), NVL(UPPER(OBJECT), ' '), NVL(ACTIVE, ' '), NVL(SEVERITY, ' '), NVL(CHKOP, ' '), NVL(CHKVAL, ' '), NVL(UNIT, ' '), NVL(CHKREP, ' '), NVL(REPUNIT, ' '), NVL(MODFLAG, '
ORA-01031: insufficient privileges
Please help me to resolve this error

Hi Patel,
check this, may be it would be helpfull to you
Error: ORA-01031: insufficient privileges
Cause:
You attempted to perform an operation for which you do not have the appropriate privileges. Some of the more common causes are:
You tried to change an Oracle username or password without having the appropriate privileges.
You tried to perform an UPDATE to a table, but you only have SELECT access to the table.
You tried to start up an Oracle database using CONNECT INTERNAL.
You tried to install an Oracle database without having the appropriate privileges to the operating-system.
Action:
The options to resolve this Oracle error are:
You can have the Oracle DBA grant you the appropriate privileges that you are missing.
You can have the Oracle DBA execute the operation for you.
If you are having trouble starting up Oracle, you may need to add the Oracle user to the dba group.
regards,
Balaram

DB13 error for CHECKDB task - BR0252E Function _stat() failed for 'D:\oracl

Hi
while trying to execute CHECKDB in Db13 i was getting the following error message
My Operating system is windows 2003 database oracle 10g
already referred to notes 952080, 134592 and subsequent notes
E:\ORACLE\NPE\ORIGLOGA\CNTRL\CNTRLNPE.DBF       26066944            4 FILE NOLINK
E:\ORACLE\NPE\ORIGLOGB\CNTRL\CNTRLNPE.DBF       26066944            4 FILE NOLINK
D:\ORACLE\NPE\SAPDATA1\CNTRL\CNTRLNPE.DBF       26066944            3 FILE NOLINK
BR0982I Database disk volumes
Directory / Raw disk                          Device      Total[KB]      Free[KB]    Used[%]   MaxNeed[KB]   MaxMiss[KB]
BR0252E Function _stat() failed for 'D:\oracle\EO1\102' at location BrDiskStatGet-1
BR0253E errno 2: No such file or directory
BR0277E Determination of disk volume status for D:\oracle\EO1\102 failed
BR0806I End of BRCONNECT processing: ceadprqb.chk 2009-03-17 18.06.25
BR0280I BRCONNECT time stamp: 2009-03-17 18.06.25
BR0804I BRCONNECT terminated with errors
if any faced simlar problem, please give let me know if you have a solution.
Regards
HM

Hello,
this type of error happens when there are permission problems. Check permission of BRtools
Check the permission of files..Check the link below for more information :
http://www-01.ibm.com/support/docview.wss?rs=667&context=SSZHVN&dc=DB560&dc=DB520&uid=swg21327498&loc=en_US&cs=UTF-8&lang=en&rss=ct667tivoli
Thanks
Anju

Db13 Error BR0981W During CheckDB

Hi Experts,
I' running ECC5.0 with Oracle.
While CheckDB in db13 I'm recieveign following error from few days.
BR0981W Not enough disk space for the total maximum size 90000.000 MB of 9 files of tablespace PSAP<SID> on disk device 5578786, missing at least 46664.094 MB
BR0981W Not enough disk space for the total maximum size 40000.000 MB of 4 files of tablespace PSAP<SID>640 on disk device 5578786, missing at least 4064.094 MB
BR0981W Not enough disk space for the total maximum size 50000.000 MB of 5 files of tablespace PSAP<SID>640 on disk device 5578783, missing at least 6934.141 MB
BR0981W Not enough disk space for the total maximum size 50000.000 MB of 5 files of tablespace PSAP<SID>640 on disk device 5578784, missing at least 5729.336 MB
I've tried to increase 5000mb the Tablespace thru BRtools, but after I'm getting same error with more diskspace required:
BR0981W Not enough disk space for the total maximum size 90000.000 MB of 9 files of tablespace PSAP<SID> on disk device 5578786, missing at least 51666.562 MB
BR0981W Not enough disk space for the total maximum size 50000.000 MB of 5 files of tablespace PSAP<SID>640 on disk device 5578786, missing at least 14066.562 MB
BR0981W Not enough disk space for the total maximum size 50000.000 MB of 5 files of tablespace PSAP<SID>640 on disk device 5578783, missing at least 6934.141 MB
BR0981W Not enough disk space for the total maximum size 50000.000 MB of 5 files of tablespace PSAP<SID>640 on disk device 5578784, missing at least 5729.336 MB
Pl. anyone suggest to solve the Problem.
Thanks in Advance.
Prakash

Hi Prakash,
You are getting the Warnings not Error because your autoextend option of datafiles is on, you can avoid this warnings by switching off the autoextend option of datafiles.
I suggest you to add new HDD to the system & move some of the datafiles from current drive to the newly attach drive so that you can avoid to get this warning message as your data files will get more space to autoextend.
Do not swith off the autoextend mode.
Hope this help.
Regards,
Rajesh

DB13 error in Job CheckDB

Hi
We made a recovery database but the jobs in DB13 are not running, i will scheduled the jobs but i get the next error in the CHECKDB job and in the UPDATESTATS job:
========================================
Job started
Step 001 started (program RSDBAJOB, variant &0000000000269, user ID IU3269)
Execute logical command BRCONNECT On host prosap2
Parameters: -u / -c -f stats -t ALL
BR0801I BRCONNECT 6.40 (32)
BR0252E Function fopen() failed for '/oracle/PDC/sapcheck/cdwhcvay.sta' at location main-9
BR0253E errno 13: Permission denied
BR0121E Processing of log file /oracle/PDC/sapcheck/cdwhcvay.sta failed
BR0806I End of BRCONNECT processing: cdwhcvay.sta2007-10-02 23.30.06
BR0280I BRCONNECT time stamp: 2007-10-02 23.30.06
BR0804I BRCONNECT terminated with errors
External program terminated with exit code 3
BRCONNECT returned error status E
Job finished
========================================
Job started
Step 001 started (program RSDBAJOB, variant &0000000000270, user ID IU3269)
Execute logical command BRCONNECT On host prosap2
Parameters: -u / -c -f check
BR0801I BRCONNECT 6.40 (32)
BR0477I Oracle pfile /oracle/PDC/920_64/dbs/initPDC.ora created from spfile /oracle/PDC/920_64/dbs/spfilePDC.ora
BR0252E Function fopen() failed for '/oracle/PDC/sapcheck/cdwhedth.chk' at location main-9
BR0253E errno 13: Permission denied
BR0121E Processing of log file /oracle/PDC/sapcheck/cdwhedth.chk failed
BR0806I End of BRCONNECT processing: cdwhedth.chk2007-10-03 06.01.07
BR0280I BRCONNECT time stamp: 2007-10-03 06.01.07
BR0804I BRCONNECT terminated with errors
External program terminated with exit code 3
BRCONNECT returned error status E
Job finished
========================================
I check the files in the directory /oracle/PDC/sapcheck/ but not exist, i do not know if i only create it will work.
Best Regards
Reynaldo Rebolledo

Hi Prince
Yes the permissions are ok and the owner and group are ok too.
drwxr-xr-x   2 orapdc   dba         1024 Oct 3 18:09 sapcheck
Best Regards
Reynaldo Rebolledo

DB13 CheckDb and Update Stats Error

Hi,
I am getting below error in CheckDb and Update stats:
Update Stats:
BR0301E SQL error -20003 at location stats_tab_collect-20, SQL statement:
'BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPCRM"', TABNAME => '"WSSOAPPROP_DARK"', ESTIMATE_PERCENT => NULL, METHOD_OPT => 'FOR ALL COLUMNS SIZE 1', DEGREE => NULL
ORA-20003: Specified bug number (5099019) does not exist
ORA-06512: at "SYS.DBMS_STATS", line 14537
ORA-06512: at "SYS.DBMS_STATS", line 14558
ORA-06512: at line 1
Check Db :
BR0301E SQL error -1031 at location BrDbdiffRead-1, SQL statement:
'PREPARE stmt_5 STATEMENT FROM'
'SELECT OBJNAME FROM "SAPSR3".DBDIFF WHERE DBSYS IN ('ORACLE', ' ') AND OBJTYPE = 'TABL' AND DIFFKIND IN ('02', '61', '99') ORDER BY OBJNAME'
ORA-01031: insufficient privileges
BR0806I End of BRCONNECT processing: ceeuoqja.chk 2010-12-17 06.30.46
BR0280I BRCONNECT time stamp: 2010-12-17 06.30.46
BR0804I BRCONNECT terminated with errors
Above both errors are of different System and both system are just get ready after System Copy of PRD Server.
Please suggest possible route cause of this error.
Shivam

for update stats issue check Note 1417124 - Error ORA-20001 in statistics class CL_SDB_ORA_UPDATE_STATS
for DB check error go through note 400241
Please search before you post your thread on SDN

Checkdb found 6 allocation errors , how to fix ?

HI Experts,
checkdb found 6 allocation errors, how to fix ?
Thanks in Advance!
Vijay

Causes
file system corruption,
underlying hardware system issues,
driver issues,
corrupted pages in memory,
problems with the SQL Server Engine.
Possible solutions
1.best solution if CHECKDB reports consistency errors is to restore from a known good backup.
2. If you cannot restore from a backup, then CHECKDB provides a feature to repair errors.
3. If system level problems such as the file system or hardware may be causing these problems, it is recommended you correct these first before restoring or running repair. 4. Allocation error in Index page, please recreate the index.
Thanks - Vanchan.Please MARK AS ANSWER, if my answer is useful to U.

Error message when I do DBCC CHECKDB

Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Msg 802, Level 17, State 20, Line 1
Error: 802, Severity: 17, State: 20. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
I guess the message means I do not have enough space in tempdb.
How can I fix it?

If possible try to restart the instance which will create new tempdb.Certain operations definitely needs large tempdb.But if you encounter operational issues you may consider shrink too.its not recommended though
http://sqlsunday.com/2013/08/11/shrinking-tempdb-without-restarting-sql-server/
Best Regards, Arun http://whynotsql.blogspot.com/
If you suspect corruption in database restating SQL Server instance or taking database offline and then bringing online could be fatal.So I would not recommend you to do that.I am not sure whether large tempdb is required or not you can check tempdb usage
when you are runing Checkdb.CHECKDB is highly resource intensive and utilizes tempdb.
Other option.as pointed by Erland, would be restore valid backup of database on clean server and run checkdb there see if it comes out clean.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

DB-13 Error ( checkdb )

Similar Messages

Maybe you are looking for