on 07-20-2009 11:06 AM
Hi,
I'm performing an import into an Oracle DB using an export from an Oracle DB of a BW system.
I'm getting the following errors from SAPDFACT, it proceeds if I "ign" the indexes of the affected tables but there are 100s of indexes, must I do this for all?
L:\usr\sap\EAD\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\Program Files\sapinst_instdir\NW04\COPY\IMPORT\SYSTEM\ABAP\ORA\NUC\DB/SAPDFACT.cmd -l C:\Program Files\sapinst_instdir\NW04\COPY\IMPORT\SYSTEM\ABAP\ORA\NUC\DB/SAPDFACT.log -stop_on_error -k 1Wegd5M50Dp01eqtd1M80Ae2
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(GSI) INFO: dbname = "EAD20090719090758 "
(GSI) INFO: vname = "ORACLE "
(GSI) INFO: hostname = "MYBWESSDEV02 "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "MYBWESSDEV02"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 1"
(GSI) INFO: machine = "4x AMD64 Level 15 (Mod 33 Step 2)"
DbSl Trace: Error 2158 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-2158 occurred when executing SQL statement (parse error offset=244)
(DB) ERROR: DDL statement failed
( CREATE INDEX "/BI0/E0FIAA_C13~P" ON "/BI0/E0FIAA_C13" ("KEY_0FIAA_C13P", "KEY_0FIAA_C13T", "KEY_0FIAA_C13U", "KEY_0FIAA_C132") PCTFREE 10 INITRANS 002 TABLESPACE STORAGE (INITIAL 0000000016 K NEXT 0000000016 K MINEXTENTS 0000000001 MAXEXTENTS UNLIMITED PCTINCREASE 0000 FREELISTS 001) )
DbSlExecute: rc = 99
(SQL error 2158)
error message returned by DbSl:
ORA-02158: invalid CREATE INDEX option
(DB) INFO: disconnected from DB
L:\usr\sap\EAD\SYS\exe\run/R3load.exe: job finished with 1 error(s)
L:\usr\sap\EAD\SYS\exe\run/R3load.exe: END OF LOG: 20090720171142
Any help is greatly appreciated.
Thanks!
- Ahmad M.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi everyone,
Issue resolved. Thanks to Sushil for pointing to another thread which also highligted the issue.
Basically, the solution is in SAP Note 885441.
I edited the SAPDFACT.SQL file and replaced the "TABLESPACE &&" entries to "TABLESPACE &DFACT&".
Explanation from SAP Support
21.07.2009 - 00:49:00 UTC+8 - Reply by SAP
Dear customer,
As you see in the statement that fails with the ora-2158 no tablespace
name is maintained. This comes from the fact that no valid entry was in
table IAORA when the create statements were generated.
Every table is assigned to a data class (tabart) in SAP, this dataclass
is in turn assigned to a container - tablespace in oracle - via table
TAORA. An index of a table inherits the dataclass, so an entry for this
is required in IAORA. These entries are <dataclass> -> <tablespace>
I guess several indexes of one data class had no entry for their
dataclass in IAORA and hence no tablespace information was saved for
the create index statement.
You will need to follow note 885441 - either editing the <tabart>.sql
file manually and adding the tablespace name - check in the source
system - or correct the entries in TAORA/IAORA and run SMIGR_CREATE
again.
Please follow the attached note closely.The error and resolution is
documented in it.
Best regards,
Carlos Wolff
SAP Active Global Support - Netweaver Web Application Server
Regards,
Ahmad M.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
> I'm getting the following errors from SAPDFACT, it proceeds if I "ign" the indexes of the affected tables but there are 100s of indexes, must I do this for all?
did you execute "smigr_create_ddl" and put the resulting SQL files to the DB/ORA directory?
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Eric,
I updated the R3load binary but I'm still facing the same issue. I also tested OPS$ as per previous suggestions but I'm still facing problems with SAPDFACT.
Extract of the log
-
L:\usr\sap\EAD\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP
L:\usr\sap\EAD\SYS\exe\run/R3load.exe: version R6.40/V1.4
Compiled Jul 5 2009 21:29:44
L:\usr\sap\EAD\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\Program Files\sapinst_instdir\NW04\COPY\IMPORT\SYSTEM\ABAP\ORA\NUC\DB/SAPDFACT.cmd -l C:\Program Files\sapinst_instdir\NW04\COPY\IMPORT\SYSTEM\ABAP\ORA\NUC\DB/SAPDFACT.log -stop_on_error -k 1Wegd5M50Dp01eqtd1M80Ae2
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(GSI) INFO: dbname = "EAD20090720060750 "
(GSI) INFO: vname = "ORACLE "
(GSI) INFO: hostname = "MYBWESSDEV02 "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "MYBWESSDEV02"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 1"
(GSI) INFO: machine = "4x AMD64 Level 15 (Mod 33 Step 2)"
DbSl Trace: Error 2158 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-2158 occurred when executing SQL statement (parse error offset=174)
(DB) ERROR: DDL statement failed
( CREATE BITMAP INDEX "/BI0/E0FIAA_C11~01" ON "/BI0/E0FIAA_C11" ("KEY_0FIAA_C11P") PCTFREE 10 INITRANS 002 TABLESPACE STORAGE (INITIAL 0000000016 K NEXT 0000000016 K MINEXTENTS 0000000001 MAXEXTENTS UNLIMITED PCTINCREASE 0000 FREELISTS 001) )
DbSlExecute: rc = 99
(SQL error 2158)
error message returned by DbSl:
ORA-02158: invalid CREATE INDEX option
(DB) INFO: disconnected from DB
L:\usr\sap\EAD\SYS\exe\run/R3load.exe: job finished with 1 error(s)
L:\usr\sap\EAD\SYS\exe\run/R3load.exe: END OF LOG: 20090721001150
-
Tried to search for SAP Notes related to this error but no luck so far.
Can any one advise if I could "ign" all the indexes in the TSK file then later on use the BW indexes repair program to fix the missing indexes?
Any help is greatly appreciated.
- Ahmad M.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
are your new tablesapce using locally managed option? Is it using ASSM?
My feeling is that you are not using the latest installation and R3LOAD tools.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi everyone,
Thank you for the prompt replies.
I edited the SAPDFACT.TSK and set the index with "err" to "ign" and the the R3load session continues till it reaches another index which outputs "err". Some indexes/table creations are "Ok" but some encounter "err".
Could this really be due to SAPUSER?
Anyway, I will still try out your suggestions and post the results.
Thank you all for your suggestions.
Regards,
Ahmad M.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The main cause of ORA-01403 is that the table SAPUSER does not contain any entries. Therefore, proceed as follows:
Use the following BRCONNECT call (BRCONNECT 6.10 or higher) to set the password consistently in SAPUSER and in the Oracle DDIC:
brconnect -u system/<password> -f chpass -o <sapowner> -p <password>
Alternatively, you can insert it in SAPUSER manually.
INSERT INTO "OPS$<sid>ADM".SAPUSER VALUES ('<sapowner>', '<password>');
Another possible cause is that SAPUSER contains incorrect entries. The system always uses the user name to select from SAPUSER. Therefore, you must ensure that the user name is always uppercase (SAPR3 or SAP<sid>) and that it corresponds exactly to the value of the environment variable dbs_ora_schema if SAP<sid> is used.
Thanks
Anish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Try to create without any other option like storage clause , incremental clause .
Ora-1403 means no data found either you are not authonticate check login sapsr3,
remote_login_password=true , ops$ user etc.
SurendraJain
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.