Is imp logging/nologging aware ?

Hi,
I'm looking a way to reduce redo generation during import via imp utility in oracle 10g (imp because exp was done in 9i so no impdp allowed).
And I wonder if setting table to NOLOGGING after importing with rows=n can reduce redo generation rate when
doing second step which is imp ... GRANTS=n INDEXES=N ROWS=y CONSTRAINTS=n ANALYZE=n commit=y ignore=y buffer=8388608 recordlength=65535 ...
Regards.
Greg

Please read Re: import with no logging option

Similar Messages

Schema Expdp-IMPdp , i have the below errors in my imp log

Hello All,
I am doing some exp/imp of schemas in a OBI environment and size around 300GB of each shema, after quiet a long time.., and not sure of the imp log errors whether to ignore or rerun my import with any changes or drop schemas and reimport ......
My IMP statement is
impdp system/********@OBIDEV schemas=ODS,DWH,STG,GEOGRAPHY directory=dumpdir dumpfile=BI2011_SCHEMAS.dmp logfile=impBI2011_SCHEMAS.log
Errors from the imp log :
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"GEOGRAPHY" already exists
ORA-31684: Object type USER:"DWH" already exists
ORA-31684: Object type USER:"STG" already exists
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
ORA-39083: Object type ROLE_GRANT failed to create with error:
ORA-01919: role 'ROLE_SRC' does not exist
Failing sql is:
GRANT "ROLE_SRC" TO "STG" WITH ADMIN OPTION
ORA-39083: Object type ROLE_GRANT failed to create with error:
ORA-01919: role 'ROLE_STG' does not exist
Failing sql is:
GRANT "ROLE_STG" TO "ODS" WITH ADMIN OPTION
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
a
--- and after some lines again the below errors, many failing sql's to created the tables ..
ORA-39083: Object type TABLE:"STG"."STG_ART_STOCK_OIG_XT" failed to create with error:
ORA-06564: object BI_SRC_FILES does not exist
Failing sql is:
CREATE TABLE "STG"."STG_ART_STOCK_OIG_XT" ("YEARWEEK" NUMBER, "ARTICLE_NUMBER" NUMBER, "BU_CODE" NUMBER, "ART_QTY_STOCK" NUMBER, "PM_CODE" VARCHAR2(10 BYTE)) ORGANIZATION EXTERNAL ( TYPE ORACLE_LOADER DEFAULT DIRECTORY "BI_SRC_FILES" ACCESS PARAMETERS ( RECORDS DELIMITED BY NEWLINE CHARACTERSET WE8MSWIN1252 STRING SIZES ARE IN BYTES BADFILE 'ART_STOCK_OIG.bad'
ORA-39083: Object type TABLE:"STG"."STG_ART_STOCK_INGKA_XT" failed to create with error:
ORA-06564: object BI_SRC_FILES does not exist
ORA-39083: Object type TABLE:"STG"."STG_ART_PMCODE_INGKA_XT" failed to create with error:
ORA-06564: object BI_SRC_FILES does not exist
Failing sql is:
CREATE TABLE "STG"."STG_IFPM_XT" ("YEAR" VARCHAR2(255 BYTE), "TERTIAL" VARCHAR2(255 BYTE), "YW" VARCHAR2(255 BYTE), "STORE_NAME" VARCHAR2(255 BYTE), "BUDGET" VARCHAR2(255 BYTE), "ACTUAL_SALES" VARCHAR2(255 BYTE), "CUSTOMERS" VARCHAR2(255 BYTE), "VISITORS" VARCHAR2(255 BYTE), "REST_SALES" VARCHAR2(255 BYTE), "EXIT_CAFE_SALES" VARCHAR2(255 BYTE), "SWE_FOOD_SALES" VARCHAR2
ORA-39083: Object type TABLE:"STG"."HFB_PA_EXT" failed to create with error:
ORA-06564: object TEMP does not exist
Failing sql is:
CREATE TABLE "STG"."HFB_PA_EXT" ("HFB_ID" NUMBER, "HFB_DESC" VARCHAR2(100 BYTE), "RA_ID" NUMBER, "RA_DESCR" VARCHAR2(100 BYTE), "PA_ID" NUMBER, "PA_DESCR" VARCHAR2(100 BYTE)) ORGANIZATION EXTERNAL ( TYPE ORACLE_LOADER DEFAULT DIRECTORY "TEMP" ACCESS PARAMETERS ( records delimited by newline
    skip 1
    fields terminated by ','
    missing field values are null
      ) LOCAT
ORA-39151: Table "GEOGRAPHY"."CAHC" exists. All dependent metadata and data will be skipped due to table_exists_action of skip
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
. . imported "ODS"."ZZ_ODS_ART_STOCK_T"                  26.81 GB 321434766 rows
imported "ODS"."ODS_PM_CODE_T":"SYS_P15548"          259.4 MB 3418214 rows (are the sys tables effected here)
Then the rows started importing ....
Share all the possible ways to avoid the above all errors in the imp log as it has to be shared with the client ,    Thanks for the swif response and help in advance.
Regards,
RanG

HI,
RanG wrote:
Hello All,
I am doing some exp/imp of schemas in a OBI environment and size around 300GB of each shema, after quiet a long time.., and not sure of the imp log errors whether to ignore or rerun my import with any changes or drop schemas and reimport ......
My IMP statement is
impdp system/********@OBIDEV schemas=ODS,DWH,STG,GEOGRAPHY directory=dumpdir dumpfile=BI2011_SCHEMAS.dmp logfile=impBI2011_SCHEMAS.log
Errors from the imp log :
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"GEOGRAPHY" already exists
ORA-31684: Object type USER:"DWH" already exists
ORA-31684: Object type USER:"STG" already exists
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
ORA-39083: Object type ROLE_GRANT failed to create with error:
ORA-01919: role 'ROLE_SRC' does not exist
Failing sql is:
GRANT "ROLE_SRC" TO "STG" WITH ADMIN OPTION
ORA-39083: Object type ROLE_GRANT failed to create with error:
ORA-01919: role 'ROLE_STG' does not exist
Failing sql is:
GRANT "ROLE_STG" TO "ODS" WITH ADMIN OPTION
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
a
--- and after some lines again the below errors, many failing sql's to created the tables ..
ORA-39083: Object type TABLE:"STG"."STG_ART_STOCK_OIG_XT" failed to create with error:
ORA-06564: object BI_SRC_FILES does not exist
Failing sql is:
CREATE TABLE "STG"."STG_ART_STOCK_OIG_XT" ("YEARWEEK" NUMBER, "ARTICLE_NUMBER" NUMBER, "BU_CODE" NUMBER, "ART_QTY_STOCK" NUMBER, "PM_CODE" VARCHAR2(10 BYTE)) ORGANIZATION EXTERNAL ( TYPE ORACLE_LOADER DEFAULT DIRECTORY "BI_SRC_FILES" ACCESS PARAMETERS ( RECORDS DELIMITED BY NEWLINE CHARACTERSET WE8MSWIN1252 STRING SIZES ARE IN BYTES BADFILE 'ART_STOCK_OIG.bad'
ORA-39083: Object type TABLE:"STG"."STG_ART_STOCK_INGKA_XT" failed to create with error:
ORA-06564: object BI_SRC_FILES does not exist
ORA-39083: Object type TABLE:"STG"."STG_ART_PMCODE_INGKA_XT" failed to create with error:
ORA-06564: object BI_SRC_FILES does not exist
Failing sql is:
CREATE TABLE "STG"."STG_IFPM_XT" ("YEAR" VARCHAR2(255 BYTE), "TERTIAL" VARCHAR2(255 BYTE), "YW" VARCHAR2(255 BYTE), "STORE_NAME" VARCHAR2(255 BYTE), "BUDGET" VARCHAR2(255 BYTE), "ACTUAL_SALES" VARCHAR2(255 BYTE), "CUSTOMERS" VARCHAR2(255 BYTE), "VISITORS" VARCHAR2(255 BYTE), "REST_SALES" VARCHAR2(255 BYTE), "EXIT_CAFE_SALES" VARCHAR2(255 BYTE), "SWE_FOOD_SALES" VARCHAR2
ORA-39083: Object type TABLE:"STG"."HFB_PA_EXT" failed to create with error:
ORA-06564: object TEMP does not exist
Failing sql is:
CREATE TABLE "STG"."HFB_PA_EXT" ("HFB_ID" NUMBER, "HFB_DESC" VARCHAR2(100 BYTE), "RA_ID" NUMBER, "RA_DESCR" VARCHAR2(100 BYTE), "PA_ID" NUMBER, "PA_DESCR" VARCHAR2(100 BYTE)) ORGANIZATION EXTERNAL ( TYPE ORACLE_LOADER DEFAULT DIRECTORY "TEMP" ACCESS PARAMETERS ( records delimited by newline
    skip 1
    fields terminated by ','
    missing field values are null
      ) LOCAT
ORA-39151: Table "GEOGRAPHY"."CAHC" exists. All dependent metadata and data will be skipped due to table_exists_action of skip
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
. . imported "ODS"."ZZ_ODS_ART_STOCK_T"                  26.81 GB 321434766 rows
imported "ODS"."ODS_PM_CODE_T":"SYS_P15548"          259.4 MB 3418214 rows (are the sys tables effected here)
Then the rows started importing ....
Share all the possible ways to avoid the above all errors in the imp log as it has to be shared with the client ,    Thanks for the swif response and help in advance.
Regards,
RanG
Because the table already exists. You can use the TABLE_EXISTS_ACTION option, so you can tell impdp what to do if the table it is trying to create already exists.
TABLE_EXISTS_ACTION={SKIP | APPEND | TRUNCATE | REPLACE}
impdp system/********@OBIDEV schemas=ODS,DWH,STG,GEOGRAPHY directory=dumpdir dumpfile=BI2011_SCHEMAS.dmp logfile=impBI2011_SCHEMAS.log table_exists_action=replace
Thank you

Logging/nologging

what is the usage of creating table with nologging, by default logging while creating table .
kindly temme the solution

Morgan, Please check the following:
a.     log_mode from v$database
b.     Is the database configured to be in force logging?
c.     Is the tablespace on which the table reside, configured to be in force logging?
In addition, here is the complete example (including ctas), using Tom Kyte mystats script:
SQL> create table nolog nologging as
2 select cast(' ' as char(2000)) as str
3 from dual connect by level <=1000;
Table created.
SQL> @c:\mystats "redo size"
NAME                                  VALUE
redo size                         8,662,356
SQL> create table yeslog logging as
2 select cast(' ' as char(2000)) as str
3 from dual connect by level <=1000;
Table created.
SQL> @c:\mystats2
NAME                                    V DIFF
redo size                        11466672        2,804,316Using the nologging in the ctas we avoided from generating a 2,804,316 of redo!
another one:
SQL> alter table nolog move;
Table altered.
SQL> @c:\mystats "redo size"
NAME                                  VALUE
redo size                        11,530,252
SQL> alter table yeslog move;
Table altered.
SQL> @c:\mystats2
NAME                                    V DIFF
redo size                        14340152        2,809,900Using the nologging in the "alter table move" we avoided from generating a 2,809,900 of redo!
and here is another one:
SQL> create index nolog_a1 on nolog(str) nologging;
Index created.
SQL> @c:\mystats "redo size"
NAME                                  VALUE
redo size                        14,409,096
SQL> create index yeslog_a1 on yeslog(str) logging;
Index created.
SQL> @c:\mystats2
NAME                                    V DIFF
redo size                        18141176        3,732,080and here is another one:
SQL> alter index nolog_a1 rebuild nologging;
Index altered.
SQL> @c:\mystats "redo size"
NAME                                  VALUE
redo size                        18,219,204
SQL> alter index yeslog_a1 rebuild logging;
Index altered.
SQL> @c:\mystats2
NAME                                    V DIFF
redo size                        21959552        3,740,348Don't forget to backup your objects, after all this nologging actions!
Amiel

Archive log / nologging/ direct path insert

Could you please confirm if following are true or correct me if my understanding is wrong:
1 ) Archive log mode and LOGGING is needed to deal with media recovery; it was not needed for instance recovery.
2) IF insert is in NO APPEND mode , redo is generated even if table is in nologging mode and database is in noachive log mode. This redo is needed for instance recovery.
3) Direct path insert skips undo generation and may skip redo generation if the object is in nologging mode.
Thanks.
In case if it is relevant , I am using Oracle 11.2.0.3.

1) Yes, Archive logs are needed for media recovery.
2 and 3) Even if the table is in nologging mode , it generates little bit of redo for index maintenance and dictionary data. Upon a restart from a failure - Oracle will read the online redo logs and replay any transaction it finds in there. That is the "roll forward" bit. The binary redo information is used to replay everything that did not get written to the datafiles. This replay included regenerating the UNDO information (UNDO is protected by redo).
After the redo has been applied, the database is typically available for use now - and the rollback phase begins. For any transaction that was being processed when the instance failed - we need to undo its changes, roll it back. We do that by processing the undo for all uncommitted transactions.
The database is now fully recovered.
Also read he following link
http://docs.oracle.com/cd/B19306_01/server.102/b14220/startup.htm
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:5280714813869

LOGGING/NOLOGGING Clause

I am running an insert statement, my insert statement selects 8 million rows from table B and inserts into table A
insert into tableA (...)
select ... from tableB
I have altered both the tables to have NOLOGGING option.
Do you think this is the right way to do or I should turn NOLOGGING on tableA and LOGGING on tableB
Since it involves the insert and select of 8 millions I am converned about the performance and time it takes for the Insert to complete
Any suggestions and inputs would help
Thanks

Nologging work only with specific operations.
http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:485221567528
http://asktom.oracle.com/pls/ask/f?p=4950:8:10968141687231771204::NO::F4950_P8_DISPLAYID,F4950_P8_CRITERIA:5280714813869
In the am444's case, if table A is in nologging mode, he need use insert /*+ APPEND */ to not generate redo.
Nicolas.
Message was edited by:
N. Gasparotto

How to log exceptions and imp logging info in Portal Service via ILogger?

Hi Experts,
I m trying to use ILogger for my application.
Information about my application:
I have created a Portal Service and exposed it as a Web Service which is deployed as a PAR file on to the SAP J2EE Engine.
I need to use the Logging facility of ILogger in this Portal Service.
I have written the following code in the Init() function of the Portal Service
public void init(IServiceContext serviceContext)
mm_logger = serviceContext.getLogger("com.persistent.pankaj");
I have put the logger.xml in the logger folder of PORTAL-INF
my logger.xml is as follows:
<Server>
<Logger name="testLog" loggerInterface="com.sapportals.portal.prt.logger.ILogger" locationName="com.sap.portal.testLog" pattern="%d # %20t %15s %m #" isActive="true">
<LoggerClass className="com.sapportals.portal.prt.logger.SimpleFileLogger" level="INFO">
<param filename="logs/com.persistent.pankaj.log" append="true">
</param>
</LoggerClass>
</Logger>
</Server>
On deploying my portal service as a web service
I m unable to get the logs.
I even dont know where will i get the log file, means wat is the exact location where i can check my log results
I m a newbie for this
Please help me out
Help will be rewarded n appreciated
-pankaj

Hi Pankaj,
In your init method try this code to create the logger:
ILogger logger = PortalRuntime.getLogger("testLog");
In your logger.xml the logger name was testLog and not com.persistent.pankaj so while creating logger you should use testLog in the above code.
By default all the logs are written to defaultTrace.log files, to check them read this:
Portal Runtime Logs
If you want to log in a seperate logfile then you should set a seperate log destination, which is not recommended on productive systems due to performance problems.
Also read these to know how to set seperate log destinations:
Netweaver Portal Log Configuration & Viewing (Part 3)
Netweaver Portal Log Configuration & Viewing (Part 1)
Netweaver Portal Log Configuration & Viewing (Part 2)
Regards,
Praveen Gudapati

Removing NOLOGGING and not explicitly designating LOGGING

We have a table that was created similar to:
create table aTableName
( col1 integer,
colN
) tablespace someName nologging;
Is there an alter command that will put the status of logging for the table the same as if it were created
create table aTableName
( col1 integer,
colN
) tablespace someName;
Also, are there three states for logging:
1. LOGGING
2. NOLOGGING
3. (undefined)
I think I am asking to put logging in the third (undefined) state?

Kent Waldrop wrote:
Is there an alter command that will put the status of logging for the table the same as if it were createdNo. All you can do is explicitly set table to LOGGING or NOLOGGING:
ALTER TABLE table_name [NO]LOGGING;
Also, are there three states for logging:
1. LOGGING
2. NOLOGGING
3. (undefined)
No, there is only LOGGING or NOLOGGING. Just open docs and you will see that default value is LOGGING. So if you create table without specifying LOGGING/NOLOGGING table will be created with LOGGING:
SQL> create table test_logging(x number)
2 /
Table created.
SQL> select logging
2 from user_tables
3 where table_name = 'TEST_LOGGING'
4 /
LOG
YES
SQL> SY.

Imp/exp ORA-12899: value too large for column

imp/exp ORA-12899: value too large for column
source :
os: linux as 4 update4
.bash_profile NLS_LANG=AMERICAN_AMERICA.US7ASCII
for run exp bill/admin001 file=bill0518.dmp bill rows=y
oracle: 10.2.1
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CHARACTERSET US7ASCII
target :
os: linux as 4 update4
.bash_profile NLS_LANG=AMERICAN_AMERICA.AL32UTF8
for run
imp bill/admin001 file=bill0518.dmp
oracle: 10.2.1
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CHARACTERSET AL32UTF8
imp log
Import: Release 10.2.0.1.0 - Production on Wed May 16 14:57:59 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc tion
With the Partitioning, Real Application Clusters, OLAP and Data Mining options
Export file created by EXPORT:V10.02.01 via conventional path
import done in US7ASCII character set and AL16UTF16 NCHAR character set
import server uses AL32UTF8 character set (possible charset conversion)
export client uses AL32UTF8 character set (possible charset conversion)
. importing BILL's objects into BILL
. . importing table "MY_SESSION" 44 rows imported
. . importing table "T1"
IMP-00019: row rejected due to ORACLE error 12899
IMP-00003: ORACLE error 12899 encountered
ORA-12899: value too large for column "BILL"."T1"."NAME" (actual: 62, maximum: 5 0)
Column 1 1
Column 2 ÖÐ¹úÈË. 0 rows impo rted
Import terminated successfully with warnings.

Yes it's probably due to different char sets
A way around it it to change the DB setup on the new database to use CHAR as default for varchar2 rows, and then use datapump to do your import/export, because datapump uses the default varchar2 type when creating tables that includes varchar2 (which is normally byte). Exp/imp uses the varchar2 type that is in the original database
Best regards
/Klaus

Error when IMPORT using INDEXFILE IMP-00009: abnormal end of export file

Hi,
I met the following error while I am doing IMPORT (creating ddl using INDEXFILE option) as.
imp system/oracle@hpfw9i file='F:\C2Prop\ProdDump20051109.dmp' fromuser=FWORKSADM touser=FWORKSADM indexfile=ddlfile.sql log=st-imp.log
. . skipping table "FWDEFECTCOMPONENT_PN21"
. . skipping table "FWDEFECTCOMPONENT_PN22"
. . skipping table "FWDEFECTCOMPONENT_PN23"
. . skipping table "FWDEFECTCOMPONENT_PN24"
. . skipping table "FWDEFECTCOMPONENT_PN25"
. . skipping table "FWDEFECTCOMPONENT_PN26"
. . skipping table "FWEQPATTRIBUTE"
. . skipping table "FWEQPATTRIBUTEHISTORY"
IMP-00009: abnormal end of export file
Import terminated successfully with warnings.
Have you ever experienced the following error message when you imported the db..?
Also I could see the import was not done successfully when I compared my ddlfileold.sql which is already done using this same dump file
My actions to make ddlfile
- I have tried three times to make ddlfile but I failed all and met the same error message.
try 1 : using 9210 version
try 2 : using 9206 version
try 3 : using 9206 version at other machine.
I need your advice and help.
Thanks,
Riaz.

This means the export dump file is corrupted.
In UNIX see this command to see whether the dump file is complete
$ tail expdat.dmp
It should have EXIT in the last line.

Import error with snapshot logs

I have an export that is a full from our production database. I'm trying to import a small subset of tables from a user to a different user. One of the tables has a snapshot log against it I believe due to the error msg in the import file. I don't care about the snapshot log I just want to get the table imported. How can I tell import to avoid the snapshot log. If this is not possible, how do I figure out what table it's says can't be found to import into.
IMP log:
. importing TYUADM's objects into DWADM
. . importing table "ZONE" 10583 rows imported
IMP-00017: following statement failed with ORACLE error 942:
"BEGIN SYS.DBMS_REPUTIL.SYNC_UP_REP('TYUADM','ZONE'); END;"
IMP-00003: ORACLE error 942 encountered
ORA-00942: table or view does not exist
ORA-06512: at "SYS.DBMS_INTERNAL_TRIGGER", line 79
ORA-06512: at "SYS.DBMS_INTERNAL_TRIGGER", line 157
ORA-06512: at "SYS.DBMS_INTERNAL_TRIGGER", line 201
ORA-06512: at "SYS.DBMS_REPUTIL", line 616
ORA-06512: at line 1
"BEGIN SYS.DBMS_SNAPSHOT_UTL.SYNC_UP_LOG('TYUADM','ZONE'); END;"
IMP-00003: ORACLE error 1435 encountered
ORA-01435: user does not exist
ORA-06512: at "SYS.DBMS_ISNAPSHOT", line 108
ORA-06512: at "SYS.DBMS_SNAPSHOT_UTL", line 1666
ORA-06512: at line 1
IMP-00000: Import terminated unsuccessfully

Oracle Server - Enterprise Edition - Version: 8.1.7.0 to 11.2.0.2 - Release: 8.1.7 to 11.2
Oracle Server - Personal Edition - Version: 8.1.7.0 to 11.2.0.2 [Release: 8.1.7 to 11.2]
Oracle Server - Standard Edition - Version: 8.1.7.0 to 11.2.0.2 [Release: 8.1.7 to 11.2]
Information in this document applies to any platform.
Symptoms
You have created a snapshot log:
SQL> connect system/manager
SQL> grant create snapshot to scott;
SQL> connect scott/tiger
SQL> create snapshot my_snap as select * from emp;
SQL> create snapshot log on scott.emp;
You run a user level export:
% exp system/manager file=exp_s.dmp log=exp_s.log owner=scott
Export: Release 9.2.0.6.0 - Production on Tue Dec 28 08:06:12 2004
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to: Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
Export terminated successfully without warnings.
You run a user level import, e.g. in a different database:
SQL> connect system/manager
SQL> create user hugo identified by hugo default tablespace
users temporary tablespace temp
quota unlimited on users;
SQL> grant create session, create table, create snapshot
to hugo;
% imp system/manager file=exp_s.dmp log=imp_s.log fromuser=scott touser=hugo
Import: Release 9.2.0.6.0 - Production on Tue Dec 28 08:08:16 2004
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to: Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
. importing SCOTT's objects into HUGO
. . importing table "BONUS" 0 rows imported
. . importing table "DEPT" 4 rows imported
. . importing table "EMP" 14 rows imported
. . importing table "MLOG$_EMP" 0 rows imported
. . importing table "MY_SNAP" 14 rows imported
. . importing table "SALGRADE" 5 rows imported
IMP-00017: following statement failed with ORACLE error 942:
"BEGIN SYS.DBMS_SNAPSHOT_UTL.SYNC_UP_LOG('SCOTT','EMP'); END;"
IMP-00003: ORACLE error 942 encountered
ORA-00942: table or view does not exist
ORA-06512: at "SYS.DBMS_SNAPSHOT_UTL", line 1589
ORA-06512: at line 1
Note that the line number in the first ORA-6512 error my differ between versions:
- in 8.1.7.4.0: ORA-06512: at "SYS.DBMS_SNAPSHOT_UTL", line 1033
- in 9.2.0.6.0: ORA-06512: at "SYS.DBMS_SNAPSHOT_UTL", line 1589
- in 10.1.0.3.0: ORA-06512: at "SYS.DBMS_SNAPSHOT_UTL", line 1599
- in 10.2.0.4.0: ORA-06512: at "SYS.DBMS_SNAPSHOT_UTL", line 1666
Also note that the same errors occur when the export was done with a table level export.
If the user SCOTT (FROMUSER) does not exist in the target database, import aborts with:
"CREATE SNAPSHOT LOG ON "SCOTT"."EMP" WITH PRIMARY KEY EXCLUDING NEW VALUES"
"USING ("MLOG$_EMP", (...left_out...))"
IMP-00003: ORACLE error 1435 encountered
ORA-01435: user does not exist
IMP-00000: Import terminated unsuccessfully
Changes
The information in this article applies to:
- Oracle Server - Enterprise Edition - Version: 8.1.7.0 to 11.2.0.x
- Oracle Server - Personal Edition - Version: 8.1.7.0 to 11.2.0.x
- Oracle Server - Standard Edition - Version: 8.1.7.0 to 11.2.0.x
This problem can occur on any platform.
Cause
Snapshots, snapshot logs, and related items are exported with the schema name explicitly given in the DDL statements, therefore, snapshots and their related items cannot be imported into a different schema.
If you attempt to use FROMUSER and TOUSER to import snapshot data, an error will be written to the Import log file and the items will not be imported.
Solution
It is expected behavior that the snapshot log cannot be imported with a FROMUSER and TOUSER import. Therefore the errors should either be prevented from happening, or be ignored:
1. Either delete the snapshot logs before the export takes place. Then run the export and import. After import completes, re-create the snapshot logs manually, and if necessary, perform a refresh of the snapshot.
2. Or ensure that the FROMUSER (SCOTT in this example) exists in the target database, so the import session does not abort with the IMP-0 error (Import terminated unsuccessfully). During the import, ignore the errors that are related to the snapshot logs. After import completes, re-create the snapshot logs manually, and if necessary, perform a refresh of the snapshot.

Imp ?

I am trying to import a dmp file in full. I believe I need sysdba rights. So I granted sysdba rights to the user i am going to import it to.
grant sysdba to Nate1;
C:\edatdmpfile>imp Nate1/pass file=ehmlink_exp.dmp log=imp.log full=yes
Import: Release 10.2.0.1.0 - Production on Wed Feb 2 10:29:51 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Express Edition Release 10.2.0.1.0 - Productio
n
Export file created by EXPORT:V10.02.01 via conventional path
IMP-00013: only a DBA can import a file exported by another DBA
IMP-00000: Import terminated unsuccessfully
I checked in toad and it say's the user Nate1 has sysdba rights.
Why is this not working???
Thanks for any help

I am connected under the sys user I execute these commands
grant IMP_FULL_DATABASE to Nate1 DEFAULT ROLE
GRANT EXPORT FULL DATABASE TO Nate1 ;
GRANT IMPORT FULL DATABASE TO Nate1 ;
GRANT DBA TO NATE1;
and I get the same error when using imp above?????
is sys user not a system user . Not sure what account would work , thought anybody connected as sysdba would work.

Logging option in materialized view

Hi all,
Anyone know about the meaning of "Logging option"(LOGGING, NOLOGGING) in Materialized view of node Snapshot in Oracle enterprise manager(Warehouse -->Summary management -->Materialized view(snapshot))
Pls explain me.
Thank you
Mcka

http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14200/clauses005.htm#i999782

Imp command and some warnings....

C:\temp>imp userid=system file=FIERROSXY.DMP log=imp.log fromuser=UFIERROS touser=UFIERROS
Connected to: Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
Export file created by EXPORT:V10.01.00 via conventional path
Warning: the objects were exported by UFIERROS, not by you
import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
. importing UFIERROS's objects into UFIERROS
. . importing table "AUTORIZA" 0 rows imported
. . importing table "BANCOS" 0 rows imported
. . importing table "CG_FORM_HELP" 0 rows imported
. . importing table "CG_REF_CODES" 0 rows imported
. . importing table "CIERRES" 0 rows imported
. . importing table "CIERRES_DETALLES" 0 rows imported
. . importing table "CLASIFICACIONES_GANADOS" 0 rows imported
. . importing table "CONDUENIOS" 0 rows imported
. . importing table "CORTES" 0 rows imported
. . importing table "CORTES_DETALLES" 0 rows imported
. . importing table "CORTES_INSTRUMENTOS" 0 rows imported
. . importing table "CUENTAS_CONTABLES" 0 rows imported
. . importing table "DOA_PICTUREDEMO" 0 rows imported
. . importing table "EMISORAS" 0 rows imported
. . importing table "FIERROS" 91324 rows imported
. . importing table "FIERROS_CLAS" 0 rows imported
. . importing table "FIERROS_IMAGEN" 103181 rows imported
IMP-00017: following statement failed with ORACLE error 959:
"CREATE TABLE "FIERROS_IMAGEN_BLOB" ("FIERROS_ID" NUMBER(7, 0), "IMAGEN" BLO"
"B, "ESTATUS" VARCHAR2(1)) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 ST"
"ORAGE(INITIAL 65536 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABL"
"ESPACE "DESA_DAT" LOGGING NOCOMPRESS LOB ("IMAGEN") STORE AS (TABLESPACE ""
"DESA_DAT" ENABLE STORAGE IN ROW CHUNK 8192 PCTVERSION 10 NOCACHE STORAGE(I"
"NITIAL 65536 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT))"
IMP-00003: ORACLE error 959 encountered
ORA-00959: tablespace 'DESA_DAT' does not exist
. . importing table "FIRMAS" 8952 rows imported
. . importing table "FIRMAS_CONDUENIOS" 0 rows imported
. . importing table "FI_CARACTER" 0 rows imported
. . importing table "FI_DIBUJO" 0 rows imported
. . importing table "FI_PRUEBA" 0 rows imported
. . importing table "FI_SIMBOLO" 0 rows imported
. . importing table "FOLIOS" 0 rows imported
. . importing table "GANADOS_ESPECIES" 0 rows imported
. . importing table "GANADOS_FIERROS" 0 rows imported
. . importing table "GANADO_PROPOSITOS" 0 rows imported
. . importing table "GANADO_RAZAS" 0 rows imported
. . importing table "GANADO_TIPOS" 20 rows imported
. . importing table "INFRAESTRUCTURAS" 0 rows imported
. . importing table "LOTE_FOLIOS" 0 rows imported
. . importing table "MEDIOS_TRANSPORTE" 7 rows imported
. . importing table "MOVIMIENTOS_FIERROS" 344326 rows imported
. . importing table "MOVIMIENTOS_PAGOS" 0 rows imported
. . importing table "MUNICIPIOS" 70 rows imported
. . importing table "NIST" 0 rows imported
. . importing table "OPERACIONES_CAJAS" 0 rows imported
. . importing table "OPERACIONES_MOVIMIENTOS" 0 rows imported
. . importing table "PARAMETROS_SISTEMA" 0 rows imported
. . importing table "PASE_DETALLE" 0 rows imported
. . importing table "PASE_MAESTRO" 0 rows imported
. . importing table "SANIDAD_DETALLE" 0 rows imported
. . importing table "TARIFA_GANADO" 0 rows imported
. . importing table "TCERTORIG" 20 rows imported
. . importing table "TIPOS_INFRAESTRUCTURAS" 0 rows imported
. . importing table "TIPOS_INSTRS_PAGOS" 0 rows imported
. . importing table "TIPOS_MOVIMIENTO" 15 rows imported
. . importing table "TIPOS_SANIDAD" 0 rows imported
. . importing table "TIPOS_SOLICITUDES" 0 rows imported
. . importing table "TIPO_GANADO" 33 rows imported
. . importing table "TIPO_SOLICITUD" 0 rows imported
. . importing table "USUARIOS" 0 rows imported
About to enable constraints...
Import terminated successfully with warnings.
some questions about:
(First i use oracle XE on windows and the file FIERROSXY.DMP are exported from Oracle 10g)
1) need create before the tablespace DESA_DAT ? if yes, where create? i know these command:
create tablespace DESA_DAT datafile 'C:\oracle\product\10.1.0\oradata\FIERROS\DESA_DAT.DBF' size 16M autoextend on next 16M maxsize 1024M segment space man agement auto extent management local;
if you see i need specify the path.... if i havent the database FIERROS i havent a path... right?
if not, wich commands need for create the table space?
2) for rerun the command first i need drop the user Fierros, then recreate it, grant some privileges, to user... and then rerun the command right?
3) anyway get warnings, the data is imported???
thanks

some questions about:
(First i use oracle XE on windows and the file
FIERROSXY.DMP are exported from Oracle 10g)
1) need create before the tablespace DESA_DAT ? if
yes, where create? i know these command:
create tablespace DESA_DAT datafile
'C:\oracle\product\10.1.0\oradata\FIERROS\DESA_DAT.DBF
' size 16M autoextend on next 16M maxsize 1024M
segment space man agement auto extent management
local;
if you see i need specify the path.... if i havent
the database FIERROS i havent a path... right?
if not, wich commands need for create the table
space?
2) for rerun the command first i need drop the user
Fierros, then recreate it, grant some privileges, to
user... and then rerun the command right?
3) anyway get warnings, the data is imported???
thanks1) No tablespace don't have to exist before import. However with one exception that is you have LOB data type in your table.
You need to precreate the tablespace
or precreate the table with LOB type in different tablespace.
2) You only need to import the table that failed, in your case, FIERROS_IMAGEN_BLOB
3) Yes, except the table report error, other tables are ok

Materialized View with No Logging Option;;; THX

Hi all,
What's the diffrence between a :
Materialized View with No Logging Option
Materialized View with Logging Option
thank you

LOGGING|NOLOGGING specifies that subsequent Direct Loader (SQL*Loader) and direct-load INSERT operations against a nonpartitioned index, a range or hash index partition, or all partitions or subpartitions of a composite-partitioned index will be logged (LOGGING) or not logged (NOLOGGING) in the redo log file.
In NOLOGGING mode, data is modified with minimal logging (to mark new extents invalid and to record dictionary changes). When applied during media recovery, the extent invalidation records mark a range of blocks as logically corrupt, because the redo data is not logged. Therefore, if you cannot afford to lose this index, you must take a backup after the operation in NOLOGGING mode.
If the database is run in ARCHIVELOG mode, media recovery from a backup taken before an operation in LOGGING mode will re-create the index. However, media recovery from a backup taken before an operation in NOLOGGING mode will not re-create the index.
An index segment can have logging attributes different from those of the base table and different from those of other index segments for the same base table.
Message was edited by:
HAGGAR

Disabling Log_Archive_Start in Archive Log Mode

Guys,
I have a Database running in Archive Log mode.
I have a situation where in I have to do bunch of bulk updates for which I dont want any logs generated.
sO I was thinking to set the intialization parameter log_archive_start to false before I run the DML updates
ALTER SYSTEM SET log_archive_start = false
after the DML is run I will turn it back on
ALTER SYSTEM SET log_archive_start = True
Do you think if this is the right to go about or would I have to switch from Archive Log Mode to No Archive Log Mode
run the DML update and then switch back to Archive Log Mode
Any comments/suggestions/inputs woo

Hello,
I would use some other way to get a full nologing behaviour.
First, ensure your tablespace is in force logging mode.
ALTER TABLESPACE data FORCE LOGGING NOLOGGING;
ALTER TABLESPACE index FORCE LOGGING NOLOGGING;
This will ensure that you're usually logging.
Set all tables/indexes to be nologging
BEGIN
FOR vRes IN (SELECT OWNER,TABLE_NAME FROM DBA_TABLES WHERE TABLESPACE_NAME='data')
LOOP
EXECUTE IMMEDIATE 'ALTER TABLE ' || vRes.OWNER || '.' || vRes.TABLE_NAME ' NOLOGGING';
END LOOP;
END;
Do even for indexes.
From now on, when you want to do your huge amount of updates/... targetting objects in tablespaces data and index, jou just have to:
ALTER TABLESPACE data NO FORCE LOGGING;
ALTER TABLESPACE indexes NO FORCE LOGGING;
- Your DML
ALTER TABLESPACE data FORCE LOGGING;
ALTER TABLESPACE indexes FORCE LOGGING.
4 commands to disable logging for every object in the tablespace.
Beware, when in NOLOGGING mode, you won't be able to "RECOVER" any of the tables. Thiis is not crash-friendly, but you'll have no redo info generated, which is what you require.
Regards,
Yoann.

Is imp logging/nologging aware ?

Similar Messages

Maybe you are looking for