on 02-06-2010 5:22 PM
Hello Team,
SAP database check finished with below warning
BR0973W Database operation alert - level: WARNING, operation: cecimlyv.log, time: 2010-01-12 13.50.57, condition: Last 'log' operation failed with rc = 3
I have searched cecimlyv.log in all directories (sapreorg ..saparch ..sapbackup ) but not found file
hostname:orasid 6> find . -name "cecimlyv.log" -print
please help me to resolve the issue
Regards
Mohsin
you can go in DB17 and disable this check if you find it annoying. look in the DBO OPERATION_TOO_OLD section.
Other than than, look in file initSID.sap. You probably delete logs with DB13's CleanupLogs and is uses parameters from file initSId.sap to define expiration time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello
<DB17>
Condition Type
Condition Name OPERATION_TOO_OLD
Check Object
Active Flag
Condition Level
Check Condition 10
Description Last successful DBA operation too old
AND
more initSID.sap
cleanup_brarchive_log = 30
retention period in days for brbackup log files
default: 30
cleanup_brbackup_log = 30
retention period in days for brconnect log files
default: 30
cleanup_brconnect_log = 30
retention period in days for brrestore log files
so please suggest me can I wait for more 2 days...to comlpete dbcheck finished sucessfully (as .log file was 28 days old)
or need to take any action
Regards
Mohsin
Hello
Sorry but no sloution found for this....
I have ran dbcheck again via Brtool and warnig still persist
tail -100 cecphkmj.chk
BR0973W Database operation alert - level: WARNING, operation: cecimlyv.log, time: 2010-01-12 13.50.57, condition: Last 'log' operation failed with rc = 3
<DB17>
showing in green
Condition Type
Condition Name OPERATION_TOO_OLD
Check Object chk
Function Database check
Active Flag YES
Condition Level
Check Condition 10
Description Last successful DBA operation too old
-
Showing in REd
Condition Type
Condition Name OPERATION_TOO_OLD
Check Object
Active Flag NO
Condition Level
Check Condition 10
Description Last successful DBA operation too old
Hello Eric,
In DB17 I have selected in RED
Condition Type
Condition Name OPERATION_TOO_OLD
Check Object
Active Flag
Condition Level
Check Condition 10
Description Last successful DBA operation too old
-
copy for object
I have selected
Condition Type
Condition Name OPERATION_TOO_OLD
Check Object log
Active Flag
Condition Level
Check Condition 10
Description Last successful DBA operation too old
Giving below error
Condition of type DBO has an incorrect function ID
Message no. Q2217
( How to Add entry ?? )
Edited by: mohsin m on Feb 17, 2010 4:34 PM
sorry for that, forget about my "log" trick, it obviously does not work.
your problem is that you have not run BRCONNECT in over 30 days,.
This means that you have not scheduled jobs in DB13
so, go into DB13 and schedule at least one weekly job.
I would recommend running CheckDB and UpdateStats at least once a day.
Pls sapcheck latest logs
-rw-rr 1 orasid dba 8197 Feb 17 00:03 cecpepqz.cln
-rw-rr 1 orasid dba 2365 Feb 17 10:00 cecpgqqs.sta
-rw-rr 1 orasid dba 32855 Feb 17 10:30 cecpgthy.chk
-rw-rr 1 orasid sapsys 36733 Feb 17 13:45 connCD1.log
-rw-rr 1 orasid dba 33066 Feb 17 13:45 cecphkmj.chk
drwxr-xr-x 2 orasid dba 4096 Feb 17 13:45 .
Daily dbcheck is running.
Hello Eric,
Today I have changed log file name and ran dbcheck but no sucess.....
-rw-rr 1 oracd1 dba 8103 Feb 19 00:03 cecpolhd.cln
-rw-rr 1 oracd1 sapsys 37143 Feb 19 10:00 connCD1.old
-rw-rr 1 oracd1 dba 2365 Feb 19 10:00 cecpqmgx.sta
-rw-rr 1 oracd1 dba 76 Feb 19 10:18 connCD1.log
-rw-rr 1 oracd1 dba 33066 Feb 19 10:18 cecpqnvq.chk
drwxr-xr-x 2 oracd1 dba 4096 Feb 19 10:18 .
but problem still persist
tail -100 cecpqnvq.chk
BR0280I BRCONNECT time stamp: 2010-02-19 10.18.20
BR0972I Checking database operations...
BR0973W Database operation alert - level: WARNING, operation: cecimlyv.log, time: 2010-01-12 13.50.57, condition: Last 'log' operation failed with rc = 3
please help
Regards
Mohsin
Dear Mohsin,
Might be got deleted as seems one month old file. but I think thats a warning file not erro.
If you want to still Warnings then run the DB check again and see if there are any look for them in current file if not be happy that no problem with your DB.
And this is not a Basis issue buddy.
Regards
Shailesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.