ORA-00942 Error during unicode export of BI 7.0

Hello Everyone,
I am doing an export of a non-unicode BI 7.0 system to convert and import it into a Unicode database. All the jobs have passed except one and I see the following error in the log file (SAPAPPL0_3.log)
/usr/sap/ABD/SYS/exe/run/R3load: START OF LOG: 20080302124247
/usr/sap/ABD/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
/usr/sap/ABD/SYS/exe/run/R3load: version R7.00/V1.4
Compiled Jun 9 2007 09:20:06
/usr/sap/ABD/SYS/exe/run/R3load -e SAPAPPL0_3.cmd -datacodepage 4102 -l SAPAPPL0_3.log -stop_on_error
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
(RSCP) WARN: UMGCONTAINER has 1 problems.
(RSCP) INFO: UMGSETTINGS nametab creation: ok.
(RSCP) INFO: Global fallback code page = 1100
(RSCP) INFO: Common character set is not 7-bit-ASCII
(RSCP) INFO: Collision resolution method is 'fine'
(RSCP) INFO: R3trans code pages = Normal
(RSCP) INFO: EXPORT TO ... code pages = Normal
(RSCP) INFO: Check for invalid language keys: active, by default
(RSCP) INFO: I18N_NAMETAB_NORM_ALLOW = 999999999
(RSCP) INFO: I18N_NAMETAB_NORM_LOG   = 1000000002
(RSCP) INFO: I18N_NAMETAB_ALT_ALLOW = 10000
(RSCP) INFO: I18N_NAMETAB_ALT_LOG    = 10003
(RSCP) INFO: I18N_NAMETAB_OLD_ALLOW = 0
(RSCP) INFO: I18N_NAMETAB_OLD_LOG    = 500
(GSI) INFO: dbname   = "ABD20070922100908
(GSI) INFO: vname    = "ORACLE                          "
(GSI) INFO: hostname = "ussbbdd5                                                        "
(GSI) INFO: sysname = "HP-UX"
(GSI) INFO: nodename = "ussbbdd5"
(GSI) INFO: release = "B.11.23"
(GSI) INFO: version = "U"
(GSI) INFO: machine = "ia64"
(GSI) INFO: instno   = "INITIAL   "
(EXP) ERROR: DbSlExeRead failed
rc = 103, table "/BIC/SZTERR_CD"
(SQL error 942)
error message returned by DbSl:
ORA-00942: table or view does not exist
(DB) INFO: disconnected from DB
/usr/sap/ABD/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/ABD/SYS/exe/run/R3load: END OF LOG: 20080302124251
When I run the following command on /BIC/SZTERR_CD, I do not get any table information back. I am not sure how to fix it though.
SELECT * FROM DBA_OBJECTS WHERE OBJECT_NAME = '/BIC/SZTERR_CD ';
I did finish all the unicode preconversion steps and also ran the SMIGR_CREATE_DDL program. I had exported recently from the same system but I never got this error during that run.
Another question is about the order in which the steps need to be performed. I completed the preconversion steps, then ran the SMIGR_CREATE_DDL program before proceeding to the export phase. Is this right or does it not matter?
Thanks again for your help!

Hello Stacy,
> When I run the following command on /BIC/SZTERR_CD, I do not get any table information back. I am not sure how to fix it though.
> SELECT * FROM DBA_OBJECTS WHERE OBJECT_NAME = '/BIC/SZTERR_CD ';
If the object does not exists on the source target database, please check if the ddic of sap still contains the table definition. (SE11 or SE14)
If yes you can set the status of the table /BIC/SZTERR_CD to "ok" in the corresponding task file.
You can not fix this problem in other way after you have started the conversion, because of the export files are already generated (with the information of the sap ddic)...
> I completed the preconversion steps, then ran the SMIGR_CREATE_DDL program before proceeding to the export phase. Is this right or does it not matter?
That was the right way.
Regards
Stefan

Similar Messages

ORA-04088: error during execution of trigger

Error Description :
We have more than 100 of records in a csv file which we are processing through a script. At the first execution let
say it generates trigger exception for five records ... when I execute the script second time those five records
are not throwing any exception but may be some other records. But consecutive trigger exception is not happening for any record . If a particular record is throwing exception at first attempt then in the second attempts it's not throwing the trigger exception.
Input file
PROPRTY_ID,NAME,OLD STREET,CITY,STATE,ZIP,NEW STREET,NEW CITY,NEW STATE,NEW ZIP
88527091,SAM PAUL SUMMU ,1061 XYZ,CITY1,ST,95626,5512 XX YY ZZ,TOWN,PA,12345-9812
Error :
88527091,SAM PAUL SUMMU ,1061 XYZ,CITY1,ST,95626,5512 XX YY ZZ,TOWN,PA,12345-9812 - PROPERTY Update Error : ORA-00001: unique constraint (PROD.PK_AUDIT_LOG) violated
ORA-06512: at "PROD.PROPERTY_AUD", line 159
ORA-04088: error during execution of trigger 'PROD.PROPERTY_AUD'
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> desc property
Name                                      Null?    Type
PROPERTY_ID                               NOT NULL NUMBER(20)
TYPE_CODE                                          VARCHAR2(10)
TYPE_PREFIX                                        VARCHAR2(10)
DWELLING_TYPE_CODE                        NOT NULL VARCHAR2(10)
DWELLING_TYPE_PREFIX                      NOT NULL VARCHAR2(10)
STREET_NUMBER                                      VARCHAR2(25)
STREET_DIRECTION                                   CHAR(2)
STREET_NAME                               NOT NULL VARCHAR2(45)
UNIT_NUMBER                                        VARCHAR2(15)
CITY_CODE                                          VARCHAR2(10)
STATE                                     NOT NULL CHAR(2)
ZIP_CODE                                           VARCHAR2(10)
UNIT_TYPE                                          VARCHAR2(10)
UNIT_PREFIX                                        VARCHAR2(10)
COUNTY_CODE                                        VARCHAR2(10)
COUNTRY_CODE                              NOT NULL VARCHAR2(10)
SQUARE_FEET                                        NUMBER(6)
NUMBER_MOTHER_LAW_UNITS                            NUMBER(6)
YEAR_BUILT                                         DATE
PROPERTY_VALUE                                     NUMBER(12)
ZIP_PLUS_4                                         VARCHAR2(4)
SFI_REQ_FLAG                                       CHAR(1)
LAST_MODIFIED                             NOT NULL DATE
LAST_MODIFIED_BY                                   VARCHAR2(31)
STANDARDIZED_STATUS                                VARCHAR2(10)
STANDARDIZED_DESC                                  VARCHAR2(200)
SQL> desc audit_log
Name                                      Null?    Type
SEQ_NO                                    NOT NULL NUMBER(20)
TABLE_NAME                                         VARCHAR2(31)
USER_STAMP                                         VARCHAR2(31)
TIME_STAMP                                         DATE
TRAN_CODE                                          CHAR(2)
RECORD1                                            VARCHAR2(2000)
RECORD2                                            VARCHAR2(2000)
FLAG_FLD                                           CHAR(1)
SFI_FLAG_FLD                                       CHAR(1)
ERROR_NUMBER                                       NUMBER
Update Query which is getting executed :
UPDATE PROPERTY
SET DWELLING_TYPE_CODE = 'SFR',
DWELLING_TYPE_PREFIX = 'DWELLING',
STREET_NUMBER = NULL,
STREET_DIRECTION = NULL,
STREET_NAME = ln_new_street_name,       -- <From input file>
UNIT_NUMBER = NULL,
CITY_CODE = ln_city_code,               -- <From other Table>
STATE = ln_new_state,                   -- <From input file>
ZIP_CODE = ln_new_zip_code,
UNIT_TYPE = NULL,
UNIT_PREFIX = NULL,
COUNTY_CODE = ln_county_code,           -- <From Other table>
COUNTRY_CODE = 1,
ZIP_PLUS_4 = ln_zip_plus_4            -- <From Input file>
WHERE PROPERTY_ID = ln_property_id;   -- <From Other table>
*NOTE :* Property.LAST_MODIFIED field is auto populate through other trigger. It does not causing any problem.
This might be helpful :
SQL> select OWNER, CONSTRAINT_NAME, TABLE_NAME,COLUMN_NAME from dba_cons_columns where CONSTRAINT_NAME='PK_AUDIT_LOG';
OWNER                          CONSTRAINT_NAME                TABLE_NAME COLUMN_NAME
PROD                           PK_AUDIT_LOG                   AUDIT_LOG          SEQ_NO
PROD_ARCH                      PK_AUDIT_LOG                   AUDIT_LOG          SEQ_NO
SQL> select SEQ_NO, trim(RECORD1), trim(RECORD2),TIME_STAMP
from audit_log where RECORD1 like '%BUTTE%' order by TIME_STAMP;
SEQ_NO
1675677212
TRIM(RECORD1)
00000000000031814095...SFR       .DWELLING ...5512 BUTTE VIEW CT                           ..15532
    .CA.95765     ...1377      .1         .....5000..20100922.SUSMSAHA                       ..
TRIM(RECORD2)
00000000000031814095...SFR       .DWELLING ...5512 BUTTE VIEW CT                           ..15532
    .CA.95765     ...1377      .1         .....5000..20100922.SUSMSAHA                       ..
TIME_STAMP
22-sep-2010
Trigger Body which is fired and throwing the exception :
create or replace trigger PROPERTY_AUD
before insert or update on PROPERTY
for each row
declare
rec1            varchar2(2000);
rec2            varchar2(2000);
tcode           char(1);
ln_seq_id       NUMBER:=Null;
ls_sql VARCHAR2(2000):=Null;
begin
select temp_audit_seq.nextval into ln_seq_id from dual;
rec1 := null;
rec2 := null;
     if user = 'NONREP_USER' then
        return;
     end if;
     if (dbms_reputil.from_remote = FALSE) then
          :NEW.last_modified := sysdate;
          if (user = 'SALESFORCE_SYNC') then
                  :new.last_modified_by := NVL(:new.last_modified_by,USER);
          else
               :new.last_modified_by := user;
          end if;
     end if;
if inserting then
rec1 :=
LPAD(:new.PROPERTY_ID, 20, '0' ) || '.' ||
RPAD(:new.TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:new.TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.DWELLING_TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:new.DWELLING_TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.STREET_NUMBER, 25, ' ' ) || '.' ||
RPAD(:new.STREET_DIRECTION, 2, ' ' ) || '.' ||
RPAD(:new.STREET_NAME, 45, ' ' ) || '.' ||
RPAD(:new.UNIT_NUMBER, 15, ' ' ) || '.' ||
RPAD(:new.CITY_CODE, 10, ' ' ) || '.' ||
RPAD(:new.STATE, 2, ' ' ) || '.' ||
RPAD(:new.ZIP_CODE, 10, ' ' ) || '.' ||
RPAD(:new.UNIT_TYPE, 10, ' ' ) || '.' ||
RPAD(:new.UNIT_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.COUNTY_CODE, 10, ' ' ) || '.' ||
RPAD(:new.COUNTRY_CODE, 10, ' ' ) || '.' ||
LPAD(:new.SQUARE_FEET, 6, '0' ) || '.' ||
LPAD(:new.NUMBER_MOTHER_LAW_UNITS, 6, '0' ) || '.' ||
TO_CHAR(:new.YEAR_BUILT, 'YYYYMMDD') || '.' ||
LPAD(:new.PROPERTY_VALUE, 12, '0' ) || '.' ||
RPAD(:new.ZIP_PLUS_4, 4, ' ' ) || '.' ||
RPAD(:new.SFI_REQ_FLAG, 1, ' ' ) || '.' ||
TO_CHAR(:new.LAST_MODIFIED, 'YYYYMMDD') || '.' ||
RPAD(:new.LAST_MODIFIED_BY, 31, ' ' ) || '.' ||
RPAD(:new.STANDARDIZED_STATUS, 10, ' ' ) || '.' ||
RPAD(:new.STANDARDIZED_DESC, 200, ' ' );
tcode := 'I';
elsif deleting then
rec1 :=
LPAD(:new.PROPERTY_ID, 20, '0' ) || '.' ||
RPAD(:new.TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:new.TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.DWELLING_TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:new.DWELLING_TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.STREET_NUMBER, 25, ' ' ) || '.' ||
RPAD(:new.STREET_DIRECTION, 2, ' ' ) || '.' ||
RPAD(:new.STREET_NAME, 45, ' ' ) || '.' ||
RPAD(:new.UNIT_NUMBER, 15, ' ' ) || '.' ||
RPAD(:new.CITY_CODE, 10, ' ' ) || '.' ||
RPAD(:new.STATE, 2, ' ' ) || '.' ||
RPAD(:new.ZIP_CODE, 10, ' ' ) || '.' ||
RPAD(:new.UNIT_TYPE, 10, ' ' ) || '.' ||
RPAD(:new.UNIT_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.COUNTY_CODE, 10, ' ' ) || '.' ||
RPAD(:new.COUNTRY_CODE, 10, ' ' ) || '.' ||
LPAD(:new.SQUARE_FEET, 6, '0' ) || '.' ||
LPAD(:new.NUMBER_MOTHER_LAW_UNITS, 6, '0' ) || '.' ||
TO_CHAR(:new.YEAR_BUILT, 'YYYYMMDD') || '.' ||
LPAD(:new.PROPERTY_VALUE, 12, '0' ) || '.' ||
RPAD(:new.ZIP_PLUS_4, 4, ' ' ) || '.' ||
RPAD(:new.SFI_REQ_FLAG, 1, ' ' ) || '.' ||
TO_CHAR(:new.LAST_MODIFIED, 'YYYYMMDD') || '.' ||
RPAD(:new.LAST_MODIFIED_BY, 31, ' ' ) || '.' ||
RPAD(:new.STANDARDIZED_STATUS, 10, ' ' ) || '.' ||
RPAD(:new.STANDARDIZED_DESC, 200, ' ' );
tcode := 'D';
else
rec1 :=
LPAD(:old.PROPERTY_ID, 20, '0' ) || '.' ||
RPAD(:old.TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:old.TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:old.DWELLING_TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:old.DWELLING_TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:old.STREET_NUMBER, 25, ' ' ) || '.' ||
RPAD(:old.STREET_DIRECTION, 2, ' ' ) || '.' ||
RPAD(:old.STREET_NAME, 45, ' ' ) || '.' ||
RPAD(:old.UNIT_NUMBER, 15, ' ' ) || '.' ||
RPAD(:old.CITY_CODE, 10, ' ' ) || '.' ||
RPAD(:old.STATE, 2, ' ' ) || '.' ||
RPAD(:old.ZIP_CODE, 10, ' ' ) || '.' ||
RPAD(:old.UNIT_TYPE, 10, ' ' ) || '.' ||
RPAD(:old.UNIT_PREFIX, 10, ' ' ) || '.' ||
RPAD(:old.COUNTY_CODE, 10, ' ' ) || '.' ||
RPAD(:old.COUNTRY_CODE, 10, ' ' ) || '.' ||
LPAD(:old.SQUARE_FEET, 6, '0' ) || '.' ||
LPAD(:old.NUMBER_MOTHER_LAW_UNITS, 6, '0' ) || '.' ||
TO_CHAR(:new.YEAR_BUILT, 'YYYYMMDD') || '.' ||
LPAD(:old.PROPERTY_VALUE, 12, '0' ) || '.' ||
RPAD(:old.ZIP_PLUS_4, 4, ' ' ) || '.' ||
RPAD(:old.SFI_REQ_FLAG, 1, ' ' ) || '.' ||
TO_CHAR(:new.LAST_MODIFIED, 'YYYYMMDD') || '.' ||
RPAD(:old.LAST_MODIFIED_BY, 31, ' ' ) || '.' ||
RPAD(:old.STANDARDIZED_STATUS, 10, ' ' ) || '.' ||
RPAD(:old.STANDARDIZED_DESC, 200, ' ' );
rec2 :=
LPAD(:new.PROPERTY_ID, 20, '0' ) || '.' ||
RPAD(:new.TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:new.TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.DWELLING_TYPE_CODE, 10, ' ' ) || '.' ||
RPAD(:new.DWELLING_TYPE_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.STREET_NUMBER, 25, ' ' ) || '.' ||
RPAD(:new.STREET_DIRECTION, 2, ' ' ) || '.' ||
RPAD(:new.STREET_NAME, 45, ' ' ) || '.' ||
RPAD(:new.UNIT_NUMBER, 15, ' ' ) || '.' ||
RPAD(:new.CITY_CODE, 10, ' ' ) || '.' ||
RPAD(:new.STATE, 2, ' ' ) || '.' ||
RPAD(:new.ZIP_CODE, 10, ' ' ) || '.' ||
RPAD(:new.UNIT_TYPE, 10, ' ' ) || '.' ||
RPAD(:new.UNIT_PREFIX, 10, ' ' ) || '.' ||
RPAD(:new.COUNTY_CODE, 10, ' ' ) || '.' ||
RPAD(:new.COUNTRY_CODE, 10, ' ' ) || '.' ||
LPAD(:new.SQUARE_FEET, 6, '0' ) || '.' ||
LPAD(:new.NUMBER_MOTHER_LAW_UNITS, 6, '0' ) || '.' ||
TO_CHAR(:new.YEAR_BUILT, 'YYYYMMDD') || '.' ||
LPAD(:new.PROPERTY_VALUE, 12, '0' ) || '.' ||
RPAD(:new.ZIP_PLUS_4, 4, ' ' ) || '.' ||
RPAD(:new.SFI_REQ_FLAG, 1, ' ' ) || '.' ||
TO_CHAR(:new.LAST_MODIFIED, 'YYYYMMDD') || '.' ||
RPAD(:new.LAST_MODIFIED_BY, 31, ' ' ) || '.' ||
RPAD(:new.STANDARDIZED_STATUS, 10, ' ' ) || '.' ||
RPAD(:new.STANDARDIZED_DESC, 200, ' ' );
tcode := 'U';
end if;
ls_sql :='
INSERT INTO AUDIT_LOG
( seq_no,
table_name,
user_stamp,
time_stamp,
tran_code,
record1,
record2)
VALUES
( :id,
:s_table_name,
:s_user_name,
:d_sysdate,
:s_tcode,
:s_rec1,
:s_rec2
EXECUTE IMMEDIATE ls_sql
USING ln_seq_id,
'PROPERTY',
user,
sysdate,
tcode,
rec1,
rec2;
end;
Your suggestion is highly appreciated ..
Edited by: Bipul on Sep 23, 2010 12:40 AM

TEMP_AUDIT_SEQ generates number with the increment of +1
Although there seems other sequence populating the AUDIT_LOG table through a different sequence with the increment of +10. So till now there are already 1179 different numbers residing in audit_log.seq_no and yet to be generated by the TEMP_AUDIT_SEQ sequence. I will look into more details.
SQL> select max(seq_no) from audit_log;
MAX(SEQ_NO)
1675689121
SQL> select TEMP_AUDIT_SEQ.nextval from dual;
   NEXTVAL
1675677285
SQL> select count(*) From audit_log where seq_no>1675677285;
COUNT(*)
      1179
SQL> select count(*) from audit_log where seq_no>1675677283 and mod(seq_no,2)=1;
COUNT(*)
      1179
SQL> select seq_no from audit_log where seq_no>1675677283 and mod(seq_no,2)=1 and rownum<12;
    SEQ_NO
1675677291
1675677301
1675677311
1675677321
1675677331
1675677341
1675677351
1675677361
1675677371
1675677381
1675677391
11 rows selected.
Thank you Lee and Herald ten Dam   ...

Oracle Collaborate Suite ORA-6502 error during loging or form submitting

Hi!
I had Oracle Collaborate Suite ORA-6502 error during loging or form submitting:
Internal error (WWC-00006)
An unexpected error has occurred (WWS-32100)
ORA-6502: ORA-06502: PL/SQL: numeric or value error: character string buffer too small (WWC-36000)
Unexpected error encountered in wwsec_api.person_info (ORA-06502: PL/SQL: numeric or value error: character string buffer too small) (WWC-41417)
Error (WWS-20000)
An unexpected error has occurred (WWS-32100)
ORA-6502: ORA-06502: PL/SQL: numeric or value error: character string buffer too small (WWC-36000)
Unexpected error encountered in wwsec_api.person_info (ORA-06502: PL/SQL: numeric or value error: character string buffer too small) (WWC-41417).
This happened when:
I was using Russian letters in OCS HTML forms (for example - in Administration provision console or in my own HTML forms)
and only I work in Linux (with UTF-8 encoding) (in Windows with win1251 encoding all is OK).
My Database NLS not-null Parameters are:
NLS_LANGUAGE      - AMERICAN
NLS_LENGTH_SEMANTICS      - BYTE
NLS_TERRITORY      - AMERICA
NLS_CHARACTERSET - AL32UTF8
NLS_NCHAR_CHARACTERSET - AL16UTF16
WHAT MUST I DO TO AVOID THIS SITUATION?
Thank
Valery

All,
It appears that the page Javascript maximum limit size was reached. The error stopped appearing after some of the page Javascript code was removed out to Application Static Files. I wonder if there exists any "direct" indicator by the system whenever the size limit has been reached?
Again, the run error only occurred when the page was loaded in "Debug" mode.
Bernard

ORA-04045: errors during recompilation/revalidation

I was applying catlog.sql and catproc.sql, but has some problem during it, and now, when I try to access a database in the sqlplus appear follow errors:
ERROR:
ORA-04045: errors during recompilation/revalidation of
SYS.DBMS_APPLICATION_INFO
ORA-06508: PL/SQL: could not find program unit being called
ORA-06512: at line 2
ORA-06508: PL/SQL: could not find program unit being called
ORA-06512: at line 2
Error accessing package DBMS_APPLICATION_INFO
Someone know about it ??
Thanks

What went wrong during catalog and catproc ?
Did you run out of space ? In that case just enable autoextension on the system tablespace datafile[s] and re-run catalog & catproc. Check the logfiles.
regards,
Ronald.
http://ronr.nl/unix-dba

Oracle Java proc ORA-04045: errors during recompilation/revalidation

hi,
I have Oracle Java stored proc called MERGE_ENTITY_AND_EVENT invoked by a trigger. It was working fine for a couple of weeks. Today it throws this generic exception. I'm not sure what changed.
Caused by: java.sql.SQLSyntaxErrorException: ORA-04045: errors during recompilation/revalidation of TLMDEV./3ba8073b_Log4JLogger
ORA-06512: at "MERGE_ENTITY_AND_EVENT", line 1
ORA-06512: at "QUOTE_TRIGGER", line 49
1. What is the root cause of this exception ?
2. Whats the solution ?
If you dont know 1 or 2, how would you go about debugging this problem ?
Thanks in advance.

The most likely cause is that something has caused the class TLMDEV./3ba8073b_Log4JLogger to become invalid and implicit invalidation does not succeed in making it valid. In general a class must be valid in order to be run and an attempt to run an invalid class (such as because your trigger calls it) will cause an attempt to validate it and if that attempt fails an ORA-04045 can be the result. Validation of a class amounts to iterating over the set of names referenced by the class and looking for a valid class by that name, perhaps recursively attempting to validate if an invalid class by that name is found. So validation of a class may amount to an attempt to validate several classes at once. If any of them fail to be validatable, which occurs if there is no class for a given referenced name then most if not all of the classes in the set being validated and certainly the top level one will fail to validate. So if things are working correctly, the ultimate reason for the ORA-04045 will prove to be that some name referenced by TLMDEV./3ba8073b_Log4JLogger or recursived by something it references will be a name for which there is no class in the database (or more precisely in the search path used which is typically the current schema followed by PUBLIC, but could be different if some of the classes involved have had explicit resolver specifications given for them). The thing to do to try to start determining what class is missing is to do the query
select owner||'.'||name||' : '||text from all_errors where type like 'JAVA%';
The first thing to look at are lines for TLMDEV./3ba8073b_Log4JLogger. These will probably show text which contains either ORA-29534 identifying a referenced class that exists but could not be recursively valid, or ORA-29521 identifying names for which there is no class. The latter are the ultimately interesting ones since the former will end up being recursively caused by them. So look at the ORA-29521s and then try to determine either why the class is missing and how to restore it or which it is now referenced when it wasn't before (which would happen if some class was changed to reference it or something that references it, recursively).

ORA-04045 : errors during recompilation/revalidation of SYS.DBMS_STANDARD

Hi,
i am on 11.5.10.2 RHEL 4.0
i tried running catalog.log on DB Tier as sys, but was not successful.
later sqlplus apps/apps would start giving
ORA-00604 : error occured at recursive SQL level 1
ORA-04045 : errors during recompilation/revalidation of SYS.DBMS_STANDARD
$sqlplus /nolog works fine... BUT
$sqlplus conn /as sysdba HANGS!!!!
Also logging via URL > after clicking on E-Business Home Page gives
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, changeOnOHSInstall and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
could anybody suggest on this error?
Thanking You
Regards,
SK

Thanks for your quick reply
status of the object: INVALID
PLSQL_V2_COMPATIBLITY is set to FALSE
Run utlrp.sql to compile all invalid objects in the database
it gave me error as follows:
SQL> @utlrp.sql
declare
ERROR at line 1
ORA -00604 : error occured at recursive SQL level 1
ORA - 04045 : errors during recompilation/revalidation of SYS.DBMS_STANDARD
CREATE TABLE utl_recomp_invalid (obj# number)
ERROR at line 1
ORA -00604 : error occured at recursive SQL level 1
ORA - 04045 : errors during recompilation/revalidation of SYS.DBMS_STANDARD
CREATE TABLE utl_recomp_sorted (obj# number, depth number)
ERROR at line 1
ORA -00604 : error occured at recursive SQL level 1
ORA - 04045 : errors during recompilation/revalidation of SYS.DBMS_STANDARD
CREATE TABLE utl_recomp_compiled(obj# number)
ERROR at line 1
ORA -00604 : error occured at recursive SQL level 1
ORA - 04045 : errors during recompilation/revalidation of SYS.DBMS_STANDARD
CREATE INDEX utl_recomp_comp_idx1 ON utl_recomp_compiled(obj#)
ERROR at line 1
ORA -00604 : error occured at recursive SQL level 1
ORA - 04045 : errors during recompilation/revalidation of SYS.DBMS_STANDARD
CREATE TABLE utl_recomp_backup_jobs (command varchar2(100), status varchar2(1000))
ERROR at line 1
ORA -00604 : error occured at recursive SQL level 1
ORA - 04045 : errors during recompilation/revalidation of SYS.DBMS_STANDARD
SELECT o.obj#, o.type#, o. owner# FROM obj# o
ERROR at line 2
ORA -00604 : error occured at recursive SQL level 1
ORA - 04045 : errors during recompilation/revalidation of SYS.DBMS_STANDARD
Edited by: mirage on Dec 4, 2008 6:45 PM

ORA-00942 error when exporting db

Hi,
Has anyone encountered the following error before? Kindly help.
Connected to: Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.7.0 - Production
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
. exporting resource costs
. exporting rollback segment definitions
. exporting database links
. exporting sequence numbers
. exporting directory aliases
. exporting context namespaces
. exporting foreign function library names
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions
EXP-00008: ORACLE error 942 encountered
ORA-00942: table or view does not exist
EXP-00024: Export views not installed, please notify your DBA
EXP-00000: Export terminated unsuccessfully
My exp parameters are full=y grants=y indexes=y rows=y

Hi,
I have executed catexp.sql but when I run the exp it produced the ff error:
Connected to: Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.7.0 - Production
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
About to export the entire database ...
. exporting tablespace definitions
. exporting profiles
. exporting user definitions
. exporting roles
. exporting resource costs
. exporting rollback segment definitions
. exporting database links
. exporting sequence numbers
. exporting directory aliases
. exporting context namespaces
. exporting foreign function library names
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions
. exporting system procedural objects and actions
. exporting pre-schema procedural objects and actions
EXP-00008: ORACLE error 21779 encountered
ORA-21779: duration not active
ORA-06512: at "SYS.DBMS_AW", line 106
ORA-06512: at "SYS.DBMS_AW", line 222
ORA-06512: at "SYS.DBMS_AW_EXP", line 264
ORA-06512: at line 1
EXP-00083: The previous problem occurred when calling SYS.DBMS_AW_EXP.schema_info_exp
. exporting cluster definitions
EXP-00056: ORACLE error 31600 encountered
ORA-31600: invalid input value EMIT_SCHEMA for parameter NAME in function SET_TRANSFORM_PARAM
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.DBMS_METADATA_INT", line 3926
ORA-06512: at "SYS.DBMS_METADATA_INT", line 4050
ORA-06512: at "SYS.DBMS_METADATA", line 836
ORA-06512: at line 1
EXP-00056: ORACLE error 31600 encountered
ORA-31600: invalid input value EMIT_SCHEMA for parameter NAME in function SET_TRANSFORM_PARAM
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.DBMS_METADATA_INT", line 3926
ORA-06512: at "SYS.DBMS_METADATA_INT", line 4050
ORA-06512: at "SYS.DBMS_METADATA", line 836
ORA-06512: at line 1
EXP-00000: Export terminated unsuccessfully

SAPInst Export Error during Unicode Conversion

Hello,
I started SAPInst, to export the source instance (for unicode conversion).
During the export preparation phase, I get the following error (in SAPInst)
ERROR
CJS-00030: Assertion failed: in component: NW_getDBInfo step: fillContextat this point the dbtype has to be != ind
ERROR
MUT-03025 Caught ESAPinstException in Modulecall:
ESAPinstException: error text undefined
ERROR
FCO-00011 The step fillContext with step key
|NW_Prepare_Export| ind| ind | ind | ind |0 |0 |NW_GetSidromProfiles |ind |ind |ind |ind |2 |0 |NW-getDBInfo |ind |ind |ind |4 |0 | fillContext was executed with status ERROR
Please help me how to rectify this error.
Thanks,
Haleem

Hello,
I recently experienced this problem, and it seems that when executing this step the <sid>adm account needs to be defined to use C shell. If its already set up to use C shell, check the <sid>adm logon scripts to make sure all the environment variables are being set correctly.
Regards,
Brad

Errors during Unicode Import

Hello,
I am getting errors during Import of Unicode Conversion. AABLG is a Cluster Table.
/usr/sap/P01/SYS/exe/run//R3load: START OF LOG: 20110110220222
/usr/sap/P01/SYS/exe/run//R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
/usr/sap/P01/SYS/exe/run//R3load: version R7.01/V1.4 [UNICODE]
Compiled Jun 19 2010 01:48:51
/usr/sap/P01/SYS/exe/run//R3load -ctf I /disk2/ABAP/DATA/SAPCLUST_1.STR /disk4/instdir/DDLORA.TPL SAPCLUST_1.TSK ORA -l SAPCLUST_1.log
/usr/sap/P01/SYS/exe/run//R3load: job completed
/usr/sap/P01/SYS/exe/run//R3load: END OF LOG: 20110110220222
/usr/sap/P01/SYS/exe/run//R3load: START OF LOG: 20110111135853
/usr/sap/P01/SYS/exe/run//R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
/usr/sap/P01/SYS/exe/run//R3load: version R7.01/V1.4 [UNICODE]
Compiled Jun 19 2010 01:48:51
/usr/sap/P01/SYS/exe/run//R3load -i SAPCLUST_1.cmd -dbcodepage 1100 -l SAPCLUST_1.log
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(CNV) WARN: you set dbcodepage '1100' but platform requires '4102'.
(CNV) WARN: dbcodepage rectified to required value.
(GSI) INFO: dbname   = "P0120110110060126                                                                                "
(GSI) INFO: vname    = "ORACLE                          "
(GSI) INFO: hostname = "ecctemp                                                         "
(GSI) INFO: sysname = "HP-UX"
(GSI) INFO: nodename = "ecctemp"
(GSI) INFO: release = "B.11.31"
(GSI) INFO: version = "U"
(GSI) INFO: machine = "ia64"
(DB) INFO: AABLG created #20110111135853
myCluster (63.25.Imp): 679: error when retrieving table description for physical table AABLG.
myCluster (63.25.Imp): 682: return code received from nametab is 2
myCluster (63.25.Imp): 302: error when retrieving physical nametab for table AABLG.
(CNV) ERROR: data conversion failed. rc = 2
(DB) INFO: AABLG~0 created #20110111135854

Hello,
you need to ensure that the Unicode conversion is done during export (target code page 4102 or 4103).
This error typically occurs if the export does not include the Unicode conversion (simple system copy with Non-Unicode).
Best regards,
Nils Buerckel
Globalization Services
SAP AG

Error during unicode conversion

Dear all,
we are facing one issue during unicode conversion. the code is as follows:
FIELD-SYMBOLS : <n> TYPE X,
                             <c> TYPE C.
DATA : a TYPE i.
DATA : x TYPE x.
MOVE <n> TO a.
a = a + 22.
MOVE a TO x.
ASSIGN x TO <c> CASTING TYPE c
and we are getting the following error:
ERROR : the length of "X" in bytes must be a multiple of the size of a Unicode character (regardless of the size of the unicode character
please guide on how this can be resolved in ECC.
Regards,
N.Jain

Hi,
here is some code to do it:
FIELD-SYMBOLS : <n> TYPE x,
                <c> TYPE c.
DATA : a TYPE i.
DATA : x TYPE x.
MOVE <n> TO a.
a = a + 22.
MOVE a TO x.
DATA:
buffer TYPE xstring,
conv TYPE REF TO cl_abap_conv_in_ce,
x_char.
buffer = x.
conv = cl_abap_conv_in_ce=>create(
       encoding = 'NON-UNICODE'
       input = buffer
CALL METHOD conv->read(
EXPORTING
    n    = 1
IMPORTING
    data = x_char
ASSIGN x_char TO <c>.
Regards
Walter Habich
Edited by: Walter Habich on Jun 10, 2008 4:09 PM

Error in unicode export...

Hi,
We are doing an inplace conversion of an ERP2005SR2 system. We have just upgraded the system from 4.6C yesterday and are now performing an unicode conversion.
Unfortunately we have an error in the unicode export... See below:
From the SAPINST_DEV.LOG file:
ERROR      2007-08-25 17:08:03 [iaxxbdbld.cpp:1001]
           CR3ldStep::startR3ldProcesses lib=iamodload module=CR3ldStep
MSC-01015 Process finished with error(s), check log file G:\usr\sap\SAPinst\CPC\EXP/SAPSDIC.log
From the SAPSDIC.LOG file:
/sapmnt/BNP/exe/R3load: START OF LOG: 20070825202939
/sapmnt/BNP/exe/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
/sapmnt/BNP/exe/R3load: version R7.00/V1.4
Compiled Aug 8 2007 00:22:00
/sapmnt/BNP/exe/R3load -datacodepage 4102 -e /usr/sap/SAPinst/CPC/EXP/SAPSDIC.cmd -l /usr/sap/SAPinst/CPC/EXP/SAPSDIC.log -inplace
DbSl Trace: CPFB755 occured. Refer to job log.
(DB) INFO: connected to DB
(EXP) INFO: check NameTab widths: Result=0.
(RC) WARNING: unexpected "ext:" entry at line 6 in file /usr/sap/SAPinst/CPC/EXP/SAPSDIC.cmd,
            entry will be ignored
(RSCP) WARN: UMGCOMCHAR read check, skip: no data found; probably old SPUMG.
(RSCP) INFO: "/usr/sap/SAPinst/CPC/EXP/SAPSDIC004.xml" created.
(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
(RSCP) INFO: UMGSETTINGS nametab creation: ok.
(RSCP) INFO: Global fallback code page = 1100
(RSCP) INFO: Common character set is not 7-bit-ASCII
(RSCP) INFO: Collision resolution method is 'fine'
(RSCP) INFO: R3trans code pages = Normal
(RSCP) INFO: EXPORT TO ... code pages = Normal
(RSCP) INFO: Check for invalid language keys: active, by default
(RSCP) INFO: I18N_NAMETAB_NORM_ALLOW = 999999999
(RSCP) INFO: I18N_NAMETAB_NORM_LOG   = 1000000002
(RSCP) INFO: I18N_NAMETAB_ALT_ALLOW = 10000
(RSCP) INFO: I18N_NAMETAB_ALT_LOG    = 10003
(RSCP) INFO: I18N_NAMETAB_OLD_ALLOW = 0
(RSCP) INFO: I18N_NAMETAB_OLD_LOG    = 500
(GSI) INFO: dbname   = "BNPSAP001                                                                                "
(GSI) INFO: vname    = "DB400                           "
(GSI) INFO: hostname = "SAP001                                                          "
(GSI) INFO: sysname = "OS400"
(GSI) INFO: nodename = "SAP001"
(GSI) INFO: release = "3"
(GSI) INFO: version = "5"
(GSI) INFO: machine = "006500039C6C"
(GSI) INFO: instno   = "0020141614"
(EXP) INFO: starting NameTab check. Allow 999999999 misses in DDNTT, 10000 misses in DDNTT_CONV_UC, 0 outdated alternate NameTab entries according to CRTIMESTMP.
(EXP) INFO: /SSF/DHEAD                        missing in DDNTT_CONV_UC
(EXP) INFO: /SSF/DTAB                         missing in DDNTT_CONV_UC
(EXP) INFO: /SSF/PTAB                         missing in DDNTT_CONV_UC
(EXP) INFO: TIBAN_ACTIVE                      missing in DDNTT_CONV_UC
(EXP) ERROR: entry for COPABBSEG                         in DDNTT is newer than in DDNTT_CONV_UC: 20070825073714 > 20070825073318
(EXP) ERROR: entry for COPABBSEG_GLX                     in DDNTT is newer than in DDNTT_CONV_UC: 20070825073756 > 20070825073318
(EXP) ERROR: entry for COPACRIT                          in DDNTT is newer than in DDNTT_CONV_UC: 20070825073801 > 20070825073318
(EXP) ERROR: entry for COPAOBJ                           in DDNTT is newer than in DDNTT_CONV_UC: 20070825073804 > 20070825073318
(EXP) ERROR: entry for EE72_COPAKEY                      in DDNTT is newer than in DDNTT_CONV_UC: 20070825073756 > 20070825072528
(EXP) ERROR: entry for JBDCHARDERI                       in DDNTT is newer than in DDNTT_CONV_UC: 20070825073804 > 20070825071134
(EXP) ERROR: entry for JBDCHARPAFO                       in DDNTT is newer than in DDNTT_CONV_UC: 20070825073805 > 20070825071134
(EXP) ERROR: entry for JBD_STR_FO_PA_CHAROBJ             in DDNTT is newer than in DDNTT_CONV_UC: 20070825073805 > 20070825071127
(EXP) ERROR: entry for JHF11_KOMP_STR                    in DDNTT is newer than in DDNTT_CONV_UC: 20070825073820 > 20070825071037
(EXP) ERROR: entry for JVKOMP                            in DDNTT is newer than in DDNTT_CONV_UC: 20070825073822 > 20070825070937
(EXP) ERROR: entry for KOMG                              in DDNTT is newer than in DDNTT_CONV_UC: 20070825073808 > 20070825070802
(EXP) ERROR: entry for KOMGF                             in DDNTT is newer than in DDNTT_CONV_UC: 20070825073823 > 20070825070802
(EXP) ERROR: entry for KOMGFNEW                          in DDNTT is newer than in DDNTT_CONV_UC: 20070825073836 > 20070825070802
(EXP) ERROR: entry for KOMGFOLD                          in DDNTT is newer than in DDNTT_CONV_UC: 20070825073838 > 20070825070802
(EXP) ERROR: entry for KOMP                              in DDNTT is newer than in DDNTT_CONV_UC: 20070825073814 > 20070825070755
(EXP) ERROR: entry for KOMPAKE                           in DDNTT is newer than in DDNTT_CONV_UC: 20070825073805 > 20070825070755
(EXP) ERROR: entry for OICIL                             in DDNTT is newer than in DDNTT_CONV_UC: 20070825073825 > 20070825070219
(EXP) ERROR: entry for OIRCPMITEM                        in DDNTT is newer than in DDNTT_CONV_UC: 20070825073826 > 20070825070148
(EXP) ERROR: entry for STR_KOMG                          in DDNTT is newer than in DDNTT_CONV_UC: 20070825073828 > 20070825063750
(EXP) ERROR: entry for SVVSC_COPA                        in DDNTT is newer than in DDNTT_CONV_UC: 20070825073757 > 20070825063738
(EXP) ERROR: entry for TRCON_CONTRACT_DATA               in DDNTT is newer than in DDNTT_CONV_UC: 20070825073846 > 20070825053905
(EXP) ERROR: entry for TRCON_CONTRACT_DATA_MM            in DDNTT is newer than in DDNTT_CONV_UC: 20070825073847 > 20070825053905
(EXP) ERROR: entry for TRCON_CONTRACT_DATA_SD            in DDNTT is newer than in DDNTT_CONV_UC: 20070825073848 > 20070825053905
(EXP) ERROR: entry for TRCON_IT_KOMP                     in DDNTT is newer than in DDNTT_CONV_UC: 20070825073830 > 20070825062450
(EXP) ERROR: entry for TRCON_OUTP_DBDATA                 in DDNTT is newer than in DDNTT_CONV_UC: 20070825073848 > 20070825053905
(EXP) ERROR: entry for WB2_EKOMP                         in DDNTT is newer than in DDNTT_CONV_UC: 20070825073831 > 20070825060540
(EXP) ERROR: entry for WCB_COND_DATA                     in DDNTT is newer than in DDNTT_CONV_UC: 20070825073848 > 20070825053905
(EXP) ERROR: entry for WCB_COND_DISP                     in DDNTT is newer than in DDNTT_CONV_UC: 20070825073839 > 20070825053905
(EXP) ERROR: entry for WCB_KEY_CHANGE                    in DDNTT is newer than in DDNTT_CONV_UC: 20070825073843 > 20070825053905
(EXP) ERROR: entry for WCB_KOMG                          in DDNTT is newer than in DDNTT_CONV_UC: 20070825073832 > 20070825053905
(EXP) ERROR: entry for WCB_KOMG_HELP                     in DDNTT is newer than in DDNTT_CONV_UC: 20070825073834 > 20070825060526
(EXP) ERROR: entry for WRF_POHF_KOMP_STY                 in DDNTT is newer than in DDNTT_CONV_UC: 20070825073844 > 20070825060357
(EXP) INFO: NameTab check finished. Result=2 #20070825203013
(EXP) INFO: check for inactive NameTab entries: Result=0.
(DB) INFO: disconnected from DB
/sapmnt/BNP/exe/R3load: job finished with 1 error(s)
/sapmnt/BNP/exe/R3load: END OF LOG: 20070825203013
I have an OSS message on "very-high" on this error, but they are not helping very much! SAP has proposed note 738858 were we set two environment variables. We have done this and that did not help.
We have upgraded and unicode converted two test systems and one development system in the last 2 months without this error.
Do you have any ideas?
Best regards
Henrik Hviid

Hello!!:
I'm doing a CU&UC (as say the CU&UC Guide), and now i'm in the phase of upgrade from 46C MDMP to ECC6.0 no unicode (later in other phase i've to change to unicode). I've generated all the SCAN's, and launch the SAPup (Upgrade Process). The phase UPGRADE/SHADOW: START OF PHASE RUN_RADCUCNT_ALL of the SAPup has created the job RADCUCNTUPG, and has been running during 20 hours. It's possible to do this phase quickly??.
Otherwise, in the chapter 3.2.2 Phase RUN_RAD_CUCNT_NEW is going to regenerated the DDIC Objects. So in the Additional Preparation Steps in SAP NW7.0 nonUC (chapter 4.1. of the guide) will be neccesary to launch again the program RADCUCNT with the variant UNICODE-02??? or we've only to do the seven steps that appears in the Guide???.
I've seen the Note 932779, 837173, about this, but i don't see the solution. In the page 7 and 8 of the Note OSS 932779, say that:
- during CU&UC nametab is touched twice, once for upgrade and once for unicode conversion (in phase RADCUCNT_ALL and in phase RADCUCNT_NEW).
- later appears that during unicode conversion preparation (SPUM4/SPUMG) RADCUCNT runs again twice.
So in the chapter 4.1 about additional preparation steps in NW7.0 non UC there is not this step (only appears7 steps). It's really neccesary in the CU&UC in this moment?
Thanks!.
Alfredo.

Error during Client Export err:

Dear Experts,
We are on 4.7 EE, Oracle 10.2.0.4 and Windows 2003 (32 Bit with 2GB RAM) (QLY system)and our database size is close to 600 GB.
I have successfully restored my PRD data to QLY and now my QLY is running fine with no hiccups.
I wanted to do the same to my DEV(which was on 9.2.0.5 now upgraded to 10G) but things are not moving good as expected.
I first tried a database backup/restore which was not successful, then i tried a system copy from QLY--> DEV but the system copy failed due to some memory issues. Finally i opted for a client export which also is failing.
All i assume is that the QLY memory is not sufficient for these activities. I have also set the parameter recommendations for 10G based on the SAP Note: 830576.
The following is the error during a client export
=====================================================================================================
2EETW000 sap_dext called with msgnr "2":
2EETW000 -
db call info -
2EETW000 function:   db_setget
2EETW000 fcode:      RT_GET (0)
2EETW000 tabname:    COEP
2EETW000 len:        3
2EETW000 key:
2EETW000 ok fetches: 33871957
2EETW000 last entry: 08710000305427330002010
2EETW000 retcode:    2
2EETW125 SQL error "4030" during "" access: "ORA-04030: out of process memory when trying to allocate 64528 bytes (sort subheap,sort key)"
4 ETW000 ROLLBACK (1852108487).
2EETP200 Export with errors, request will not be imported
1 ETP150 MAIN EXPORT
1 ETP110 end date and time   : "20100512075209"
1 ETP111 exit code           : "12"
=====================================================================================================
When i searched based on the SQL error 4030 i had many replies suggesting to increase my pga and other memory related parameters.
Can anyone suggest me the optimal parameter recommendations based on the size of my RAM(2GB) for my Oracle and SAP please.
We are in the process of increasing it to 4GB very soon.
Awaiting a helpful reply
Thanks in advance
Hunky

If it is working on your QLY system, just use the same parameter set as there..
Kind regards,
Mark

Trying to change the Release/Debug connection string (ORACLE) of a VS13 Lightswitch project. Getting ORA-00942 error...

Hello,
i try to change the connection string of a Lightswitch 2013 project. I have a database for developers and a 'productive' database for releases. Both are similar (table names, entries etc..) and they are from ORACLE. First i attached the developer database
as an external source. Everything works fine. Now I'm trying to change the connection string whether my application is in a release state or in a developer state.
I found a hint in the following question to solve that issue: Question
from a LS-User
It is possible to change the connection string during the runtime. I tried it out and added to my DataBaseService.lsml.cs:
partial void DataBase_InitializingConnection(DatabaseConnectionState state)
state.ConnectionString = "DATA SOURCE=DB.productive;PASSWORD=password;PERSIST SECURITY INFO=True;USER ID=USER_PROD";
Well, Lightswitch is using the new connection. But when i run the application, i am getting the error "ORA-00942: table or view does not exist". The views and tables definitely exist. The two schemas are the same. So what am i doing wrong?
Regards from Munich

HI Munich,
Welcome to Lightswitch forum.
According to your description above, you want to connect to external datasource in Lightswitch application.
Oracle is not a supported data source for LightSwitch, it's recommended to use SQL Server database.
If you want to change the connection string, you can update the connection string for a data source using the data source wizard. For example in VS2013:
Please let me know if there is anything that I can do to help.
Best regards,
Angie
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

ORA-00942 error on truncating a table with a XML Index

Oracle Version: 11.2.0.1.0
When truncate command fails with error "ORA-00942: table or view does not exist" when run against a table with an XML Index defined
SQL> CREATE TABLE XML_TEST
2 (
3 ID INTEGER,
4 TESTXML SYS.XMLTYPE
5 );
Table created.
SQL> truncate table XML_TEST;
Table truncated.
SQL> CREATE INDEX xmlindex ON XML_TEST(TESTXML)
2 indextype IS xdb.xmlindex
3 parameters ('PATH TABLE MY_PATH_TABLE');
Index created.
SQL> truncate table XML_TEST;
truncate table XML_TEST
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> Drop Index xmlindex;
Index dropped.
SQL> truncate table XML_TEST;
Table truncated.

No, I don't think that explanation is correct. I don't think it has to do with user privs. besides, we don't
adjust rowids on an import -- we recreate the index, just like a b-tree index import would.
This should be working. It's most likely a bug in our (i.e. Text) import code -- SYS.XMLTYPE is a little
strange because under the covers it's actually a function-based index.
I will test it out and file a bug if I can reproduce the behavior on solaris.

Intermittent ORA-00942 error

Hi,
I'm getting an intermittent ORA-00942 (Table or View Does Not Exist) error in Oracle 9i. We're getting it in several different packages, and they all have one thing in common.
They are all either joining to a table type that had previously been populated with a BULK COLLECT INTO or a temp table that was populate with a CAST (from the same table type) or has a TABLE CAST directly in the join.
This is the type:
CREATE OR REPLACE TYPE fe_id_tab AS TABLE OF INTEGER NOT NULL;
This is the table:
create global temporary table FE_TMP_ID
ID INTEGER not null
on commit delete rows;
Again, this is an intermittent error. It only happens occasionally, and when it does happen, if you immediately run the same query, it works fine.
Thanks,
Karin

smuthuku wrote:
The customer is getting the below error in the alert log intermittently when running utlrp script in 11.2.0.2
ORA-12012: error on auto execute of job "SYS"."UTL_RECOMP_SLAVE_24"
ORA-00942: table or view does not exist
As this happens in a production environment, the customer doesn't want to turn on the tracing but wants to know
if this is a problem with the data dictionary or someother issue. Any inputs appreciated.
Yes, it is a problem with data dictionay or some other issue.
do as below so we can know complete Oracle version & OS name.
Post via COPY & PASTE complete results of
SELECT * from v$version;

ORA-00942 Error during unicode export of BI 7.0

Similar Messages

Maybe you are looking for