Knowledge Management

Question:
Hi,
after install SAP46B oracle Solaris, I try to do a DB13 check DB:
log:
DB Operations:
aly (#1)
failed in last run.
opt (#1)
failed in last run.
rsi (#1)
failed in last run.
rtc (#1)
failed in last run.
rtd (#1)
failed in last run.
return> to continue ...
Alert log messages:
ORA-1113
ORA-1115
ORA-1122
ORA-1135
ORA-1149
ORA-1555
ORA-1562
ORA-1578
ORA-272
ORA-3113
ORA-376
ORA-600
ORA-Checkpoint not complete
can someone give me a track?
Answer:
try to do check from sapdba, there is a lot of ORA errors and differents type of errors -rollback segments, space...
put more information please
Answer:
with sapdba, it's same.
more info:
2003-02-04 16.24.28 Check of all tablespaces
(Checking critical number of new extents: 1):
SAPDBA: The following tables/indexes/clusters would overflow the tablespace by allocating the number of extents shown in the appropriate column:
TABLESPACE SEGMENT TYPE EXTENTS NEXT (K)
PSAPCLUD CDCLS TABLE 1<= 1 10240
PSAPCLUD EDI40 TABLE 1<= 1 10240
Total: 2 object(s).
SAPDBA: Alert - CRITICAL SEGMENTS:
SEGMENT(S) CDCLS, EDI40 WOULD CAUSE A TABLESPACE OVERFLOW BY ALLOC. UP TO 1 NEXT EXTENT(S)
*********************** End of check of all tablespaces ****
2003-02-04 16.24.29 Check of tables and indexes without opt stats SAPDBA: Using control table DBSTATC
for taking optimizer settings into account
SAPDBA: No opt. statistics for the following tables: PLAN_TABLE
SAPDBA: Alert - NO_OPT_STATS for 1 tables: PLAN_TABLE
SAPDBA: All indexes have a valid optimizer statistics
2003-02-04 16.24.34 Check of failed DB Oper. since 2003-
2003-02-04 16.24.34 Last successful DB Operations too old:
SAPDBA: Last successful DB operation(s) on 'aly' are younger than threshhold: O.K.
SAPDBA: Alert - DB Operation opt never started or finished successfully **** End of checking DB Operations ********
Available disk space in SAPDATA directories:
2003-02-04 16.24.35 Checking init.ora parameters
SAPDBA: Alert - Parameter LOG_CHECKPOINT_INTERVAL is set to 300000 < 3000000000
SAPDBA: Alert - Parameter OPTIMIZER_FEATURES_ENABLE is set to 8.0.0 (not to proper value 8.0.4)
SAPDBA: Alert - Parameter HASH_JOIN_ENABLED is set to TRUE (not to proper value FALSE)
SAPDBA: 3 out of 27 checked init.ora parameters are not set properly
###############################################
******************* Alert Summary
SAPDBA: Warning - Alert conditions were detected
CRITICAL_SEGS
NOARCHIVELOG_MODE
NO_OPT_STATS
SAPDBA: Warning - Oracle profile parameters are not set properly
thanks for your help
I don't understood: it's a new install with DBSIZE by default.
is it normal to get so much error?
Answer:
How do u do the installation? It is not the first installation, isnt it?
Are you running a backup? Or did u running and it didnt end correctly?
Are u shutdown the machine?
Answer:
it's a first install.
I got a pb, so, I'm obliged to uninstall SAP and oracle.
I re install solaris on local disk.
and re install SAP and oracle.
but system is new.
now, I can't do a backup (DB13 out)
I have only the 000 client with DDIC. I wait to install language before create new client.
so nobody use this system yet.
have you an explaination?
I've installed oracle by default.
Answer:
I've never execute
check optimiser stat
adapt next extens
check database
which parameters for 'check optimiser stat"?
is it dangerous?
for information, i replaced parameters:
db_name = DEFAULT by db_name = SU7 in init.ora
log_checkpoint_initial = 300000 by 3000000000 in initSU7.ora (after the message of error DB13)
i haven't found parameters :
OPTIMIZER_FEATURES_ENABLE and HASH_JOIN_ENABLED
I succes to parameters initSU7.sap and do a backup with DB13:
just a question: i set compress = yes (is it OK?)
lot of thanks
Answer:
Problem 1. Check of all tablespaces (Checking critical number of new extents: 1): SAPDBA: The following tables/indexes/clusters would overflow the tablespace by allocating the number of extents shown in the appropriate column: TABLESPACE SEGMENT TYPE EXTENTS NEXT (K)
PSAPCLUD CDCLS TABLE 1<= 1 10240
PSAPCLUD EDI40 TABLE 1<= 1 10240
Total: 2 object(s).
SAPDBA: Alert - CRITICAL SEGMENTS:
SEGMENT(S) CDCLS, EDI40 WOULD CAUSE A TABLESPACE OVERFLOW BY ALLOC. UP TO 1 NEXT EXTENT(S)
Here you have to increase size of PSAPCLUD tablespace
Problem 2:SAPDBA: No opt. statistics for the following tables: PLAN_TABLE
SAPDBA: Alert - NO_OPT_STATS for 1 tables: PLAN_TABLE
SAPDBA: All indexes have a valid optimizer statistics
2003-02-04 16.24.34 Check of failed DB Oper. since 2003-
2003-02-04 16.24.34 Last successful DB Operations too old:
SAPDBA: Last successful DB operation(s) on 'aly' are younger than threshhold: O.K.
SAPDBA: Alert - DB Operation opt never started or finished successfully
This is only a warning. Dont mind of that
Problem 3:Available disk space in SAPDATA directories:
2003-02-04 16.24.35 Checking init.ora parameters
SAPDBA: Alert - Parameter LOG_CHECKPOINT_INTERVAL is set to 300000 < 3000000000
SAPDBA: Alert - Parameter OPTIMIZER_FEATURES_ENABLE is set to 8.0.0 (not to proper value 8.0.4)
SAPDBA: Alert - Parameter HASH_JOIN_ENABLED is set to TRUE (not to proper value FALSE)
These last parameters have to be write directly in the initSID.ora file
Answer:
SAPDBA: Alert - Parameter LOG_CHECKPOINT_INTERVAL is set to 300000 < 3000000000
SAPDBA: Alert - Parameter OPTIMIZER_FEATURES_ENABLE is set to 8.0.0 (not to proper value 8.0.4)
SAPDBA: Alert - Parameter HASH_JOIN_ENABLED is set to TRUE (not to proper value FALSE)
If you are on Oracle 8.1.x, these warnings are not true. Uyou must change these values on DB17... make searches on OSS to find appropriate notes.
Snowy