Import Successful with warnings....ORA-01658 error..

Friends,
OS: RHEL AS 3.0
DB: Oracle 9iR2
When i try to import the dump, i am getting the below message.
"Import was successful with warnings"
when i check the log file there is
IMP-00017: following statement failed with oracle error 1658:
IMP-00003: ORACLE error 1658 encountered
ORA-01658: unable to create INITIAL extent for segment in tablespace PROD_DEFAULTPlease check the below, this is what i did before importing.
I want to import only the table structures without rows from the user "SMS" to "NMS".
After creating the below tablespace the free space in "/u02" is 3GB.
AM i have to change any value in the below statement?
CREATE TABLESPACE "PROD_DEFAULT" DATAFILE
  '/u02/oradata/PROD_DEFAULT.dbf' SIZE 3072M REUSE
  LOGGING ONLINE PERMANENT BLOCKSIZE 8192
  EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
CREATE TEMPORARY TABLESPACE "PROD_TEMP" TEMPFILE
  '/u02/oradata/PROD_TEMP.dbf' SIZE 3072M REUSE
  EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1048576
CREATE USER "NMS" IDENTIFIED BY "SDF345345KLSDSD8K" DEFAULT
TABLESPACE "PROD_DEFAULT"
TEMPORARY TABLESPACE "PROD_TEMP"
GRANT CONNECT,RESOURCE TO NMS
[oracle@linuxdb oracle]$ imp system/password file=/u02/today1.dmp
log=/u02/today1.log fromuser=sms touser=nms rows=n buffer=8000000 commit=yNote:
Even if i omit "buffer" and "commit" the same error occurs.
where im making a mistake? Is there any changes i have to made in the create tablespace statement.
Please point out the mistake.
thanks & regards

not for a single statement. for all the statements
its showing the error.instead of 512 tables
structures, only 490 tables structures were created.Because it was not able to allocate contiguous space in the tablespace.
>
actually i want to import "NMS_DEFAULT" tablespace's
table structures to "PROD_DEFAULT" tablespace.
also I want to import only the table structures
without rows from the user "SMS" to "NMS".Use FROMUSER/TOUSER for this and set the default tablespace for NMS as PROD_DEFAULT.
Now specify rown=N while running import or at the time of running export itself.
i created the "NMS_DEFAULT" tablespace with 3072M.
so i created the "PROD_DEFAULT" tablespace with the
same size.
actually i created the "PROD_DEFAULT" tablespace
using below output.
"select
dbms_metadata.get_ddl('TABLESPACE','NMS_DEFAULT')
from dual"You didnt allocate sufficient space to the tablespace, i guess.
Amardeep Sidhu
http://www.amardeepsidhu.com
Corrected a mistake...
Message was edited by:
Amardeep Sidhu

Similar Messages

  • Export is terminating successfully with warnings

    Hi Gurus,
    Export is getting terminated successfully with warnings. Below errors are recorded in export file
    EXP-00008: ORACLE error 4063 encountered
    ORA-04063: package body "SYS.LT_EXPORT_PKG" has errors
    ORA-06508: PL/SQL: could not find program unit being called: "SYS.LT_EXPORT_PKG"
    ORA-06512: at line 1
    EXP-00083: The previous problem occurred when calling SYS.LT_EXPORT_PKG.system_info_exp
    EXP-00008: ORACLE error 6550 encountered
    ORA-06550: line 1, column 13:
    PLS-00201: identifier 'EXFSYS.DBMS_EXPFIL_DEPASEXP' must be declared
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    EXP-00083: The previous problem occurred when calling EXFSYS.DBMS_EXPFIL_DEPASEXP.system_info_exp
    EXP-00008: ORACLE error 4063 encountered
    ORA-04063: package body "SYS.LT_EXPORT_PKG" has errors
    ORA-06508: PL/SQL: could not find program unit being called: "SYS.LT_EXPORT_PKG"
    ORA-06512: at line 1
    EXP-00083: The previous problem occurred when calling SYS.LT_EXPORT_PKG.system_info_exp
    EXP-00008: ORACLE error 6550 encountered
    ORA-06550: line 1, column 13:
    PLS-00201: identifier 'EXFSYS.DBMS_EXPFIL_DEPASEXP' must be declared
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    EXP-00083: The previous problem occurred when calling EXFSYS.DBMS_EXPFIL_DEPASEXP.system_info_exp
    . exporting pre-schema procedural objects and actions
    EXP-00008: ORACLE error 6550 encountered
    ORA-06550: line 1, column 13:
    PLS-00201: identifier 'EXFSYS.DBMS_EXPFIL_DEPASEXP' must be declared
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    EXP-00083: The previous problem occurred when calling EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp
    EXP-00008: ORACLE error 4063 encountered
    ORA-04063: package body "SYS.LT_EXPORT_PKG" has errors
    ORA-06508: PL/SQL: could not find program unit being called: "SYS.LT_EXPORT_PKG"
    ORA-06512: at line 1
    EXP-00083: The previous problem occurred when calling SYS.LT_EXPORT_PKG.schema_info_exp
    EXP-00008: ORACLE error 6550 encountered
    ORA-06550: line 1, column 13:
    PLS-00201: identifier 'DMSYS.DBMS_DM_MODEL_EXP' must be declared
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    EXP-00083: The previous problem occurred when calling DMSYS.DBMS_DM_MODEL_EXP.schema_info_exp
    Please help me how to resolve this.
    Thanks,
    Dasarath

    Pl post details of OS and database versions, along with the complete export command. Has this ever worked before ? If so, what has changed since the last successful export ?
    See these MOS Docs
    298107.1 - Export Is Giving Errors Exp-00008 ORA-4068 ORA-4063 on SYS.LT_EXPORT_PKG
    740818.1 - Full Database Export Raises Warnings EXP-8 ORA-6550 PLS-201 Identifier 'SYS.LT_EXPORT_PKG' Must be Declared
    312317.1 - Export Failing with ORA-06550 and PLS-00201 on LT_EXPORT_PKG
    HTH
    Srini

  • Backup Error "Return Code 0001 Success with warnings"

    Hi All,
    I have a problem while taking backup using brtools .We scheduled a full offline backup and in DB12 when i check the status of last successful backup then it shows like
    Return Code 0001 Success with warnings
    System: ECC6
    OS:Solaris
    DB:Oracle10g
    What does this error mean there is no warning in log file also.
    Anybody have any idea??
    Thanks in Advance

    Hi,
    Thanks for your reply .
    Here is my  Logfile
    TOO LONG .....
    BR0051I BRBACKUP 7.00 (32)
    BR0055I Start of database backup: bdzgizji.aff 2008-11-14 22.18.54
    BR0484I BRBACKUP log file: /oracle/<MYSID>/sapbackup/bdzgizji.aff
    BR0477I Oracle pfile /oracle/<MYSID>/102_64/dbs/init<MYSID>.ora created from spfile /oracle/<MYSID>/102_64/dbs/spfile<MYSID>.ora
    BR0286W Size 2306875392 of file /oracle/<MYSID>/sapdata1/sr3700_2/sr3700.data2 is different from Oracle file size 2222989312
    BR0101I Parameters
    Name                           Value
    oracle_sid                     <MYSID>
    oracle_home                    /oracle/<MYSID>/102_64
    oracle_profile                 /oracle/<MYSID>/102_64/dbs/init<MYSID>.ora
    sapdata_home                   /oracle/<MYSID>
    sap_profile                    /oracle/<MYSID>/102_64/dbs/init<MYSID>.sap
    backup_mode                    ALL
    backup_type                    offline_force
    backup_dev_type                util_file
    util_par_file                  /oracle/<MYSID>/102_64/dbs/init<MYSID>.utl
    system_info                    ora<MYSID>/ora<MYSID> DBD112 SunOS 5.10 Generic_127127-11 sun4v
    oracle_info                    <MYSID> 10.2.0.2.0 8192 2867 21991272 DBD112 UTF8 UTF8
    sap_info                       700 SAPSR3 0002LK0003<MYSID>0011Q07320361650013NetWeaver_ORA
    make_info                      sun_64 OCI_102 Feb  6 2008
    command_line                   brbackup -u / -c -d util_file -t offline_force -m all -a -sd -c
    BR0116I ARCHIVE LOG LIST before backup for database instance <MYSID>
    Parameter                      Value
    Database log mode              Archive Mode
    Automatic archival             Enabled
    Archive destination            /oracle/<MYSID>/oraarch/<MYSID>arch
    Archive format                 %t_%s_%r.dbf
    Oldest online log sequence     2864
    Next log sequence to archive   2867
    Current log sequence           2867             SCN: 21991272
    Database block size            8192             Thread: 1
    Current system change number   22007193         ResetId: 665869765
    BR0118I Tablespaces and data files
    Tablespace     TS-Status  F-Status  File                                                       Size   Id.     Device  Link    Type       MaxSize     IncrSize  BlkSize
    PSAPSR3        ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata1/sr3_1/sr3.data1                 2097160192    4     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata1/sr3_2/sr3.data2                 2097160192    5     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata1/sr3_3/sr3.data3                 2097160192    6     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata1/sr3_4/sr3.data4                 2097160192    7     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata1/sr3_5/sr3.data5                 2097160192    8     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata2/sr3_10/sr3.data10               2118131712   13     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata2/sr3_6/sr3.data6                 2097160192    9     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata2/sr3_7/sr3.data7                 2097160192   10     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata2/sr3_8/sr3.data8                 2097160192   11     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata2/sr3_9/sr3.data9                 2097160192   12     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata3/sr3_11/sr3.data11               2181046272   14     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata3/sr3_12/sr3.data12               2369789952   15     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata3/sr3_13/sr3.data13               2181046272   16     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata3/sr3_14/sr3.data14               2202017792   17     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata3/sr3_15/sr3.data15               2118131712   18     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata4/sr3_16/sr3.data16               2306875392   19     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata4/sr3_17/sr3.data17              10485768192   20     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata4/sr3_18/sr3.data18              10485768192   21     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata4/sr3_19/sr3.data19               3292536832   22     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3        ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata4/sr3_20/sr3.data20               2097160192   23     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3700     ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata1/sr3700_1/sr3700.data1           2160074752   24     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3700     ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata1/sr3700_2/sr3700.data2           2222989312   25     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3700     ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata1/sr3700_3/sr3700.data3           2411732992   26     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3700     ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata1/sr3700_4/sr3700.data4          10485768192   27     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3700     ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata2/sr3700_5/sr3700.data5          10485768192   28     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3700     ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata2/sr3700_6/sr3700.data6          10485768192   29     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3700     ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata2/sr3700_7/sr3700.data7           9374277632   30     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3700     ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata2/sr3700_8/sr3700.data8           2789220352   31     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3700     ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata3/sr3700_10/sr3700.data10         2327846912   33     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3700     ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata3/sr3700_11/sr3700.data11         2411732992   34     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3700     ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata3/sr3700_12/sr3700.data12         2181046272   35     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3700     ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata3/sr3700_9/sr3700.data9           3187679232   32     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3700     ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata4/sr3700_13/sr3700.data13         2160074752   36     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3700     ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata4/sr3700_14/sr3700.data14         2327846912   37     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3700     ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata4/sr3700_15/sr3700.data15         2222989312   38     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3700     ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata4/sr3700_16/sr3700.data16         2139103232   39     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPSR3700     ONLINE*    ONLINE    /oracle/<MYSID>/sapdata4/sr3700_17/sr3700.data17         2097160192   43     9764872  NOLINK  FILE             0            0     8192
    PSAPSR3700     ONLINE*    ONLINE    /oracle/<MYSID>/sapdata4/sr3700_18/sr3700.data18         2097160192   44     9764872  NOLINK  FILE             0            0     8192
    PSAPSR3700     ONLINE*    ONLINE    /oracle/<MYSID>/sapdata4/sr3700_19/sr3700.data19         2097160192   45     9764872  NOLINK  FILE             0            0     8192
    PSAPSR3USR     ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata1/sr3usr_1/sr3usr.data1             20979712   40     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPTEMP       ONLINE#    ONLINE+   /oracle/<MYSID>/sapdata2/temp_1/temp.data1               2097160192   -1     9764872  NOLINK  FILE   10485760000     20971520     8192
    PSAPUNDO       ONLINE-    ONLINE+   /oracle/<MYSID>/sapdata3/undo_1/undo.data1               9374277632    2     9764872  NOLINK  FILE   10485760000     20971520     8192
    SYSAUX         ONLINE*    ONLINE+   /oracle/<MYSID>/sapdata1/sysaux_1/sysaux.data1            272637952    3     9764872  NOLINK  FILE   10485760000     20971520     8192
    SYSAUX         ONLINE*    ONLINE    /oracle/<MYSID>/sapdata1/sysaux_2/sysaux.data2           2097160192   42     9764872  NOLINK  FILE             0            0     8192
    SYSTEM         ONLINE*    SYSTEM+   /oracle/<MYSID>/sapdata1/system_1/system.data1            880812032    1     9764872  NOLINK  FILE   10485760000     20971520     8192
    SYSTEM         ONLINE*    SYSTEM    /oracle/<MYSID>/sapdata1/system_2/system.data2           2097160192   41     9764872  NOLINK  FILE             0            0     8192
    BR0119I Redo log files
    File                                                Size  Group     Device  Status    Link    Type
    /oracle/<MYSID>/origlogA/log_g11m1.dbf              52429312    1      9764872  INUSE     NOLINK  FILE
    /oracle/<MYSID>/mirrlogA/log_g11m2.dbf              52429312    1      9764872  INUSE     NOLINK  FILE
    /oracle/<MYSID>/origlogB/log_g12m1.dbf              52429312    2      9764872  INUSE     NOLINK  FILE
    /oracle/<MYSID>/mirrlogB/log_g12m2.dbf              52429312    2      9764872  INUSE     NOLINK  FILE
    /oracle/<MYSID>/origlogA/log_g13m1.dbf              52429312    3      9764872  INUSE     NOLINK  FILE
    /oracle/<MYSID>/mirrlogA/log_g13m2.dbf              52429312    3      9764872  INUSE     NOLINK  FILE
    /oracle/<MYSID>/origlogB/log_g14m1.dbf              52429312    4      9764872  INUSE     NOLINK  FILE
    /oracle/<MYSID>/mirrlogB/log_g14m2.dbf              52429312    4      9764872  INUSE     NOLINK  FILE
    BR0120I Control files
    File                                                Size   Id.      Device  Link    Type
    /oracle/<MYSID>/origlogA/cntrl/cntrl<MYSID>.dbf         15908864    0      9764872  NOLINK  FILE
    /oracle/<MYSID>/origlogB/cntrl/cntrl<MYSID>.dbf         15908864    0      9764872  NOLINK  FILE
    /oracle/<MYSID>/sapdata1/cntrl/cntrl<MYSID>.dbf         15908864    0      9764872  NOLINK  FILE
    BR0280I BRBACKUP time stamp: 2008-11-14 22.18.57
    BR0057I Backup of database: <MYSID>
    BR0058I BRBACKUP action ID: bdzgizji
    BR0059I BRBACKUP function ID: aff
    BR0110I Backup mode: ALL
    BR0077I Database files for backup:
    /oracle/<MYSID>/origlogA/log_g11m1.dbf
    /oracle/<MYSID>/origlogB/log_g12m1.dbf
    /oracle/<MYSID>/origlogA/log_g13m1.dbf
    /oracle/<MYSID>/origlogB/log_g14m1.dbf
    /oracle/<MYSID>/origlogA/cntrl/cntrl<MYSID>.dbf
    BR0061I 51 files found for backup, total size 146335.533 MB
    BR0143I Backup type: offline_force
    BR0130I Backup device type: util_file
    BR0109I Files will be saved by backup utility
    BR0289I BRARCHIVE will be started at the end of processing
    BR0126I Unattended mode active - no operator confirmation required
    BR0280I BRBACKUP time stamp: 2008-11-14 22.18.57
    BR0307I Shutting down database instance <MYSID> ...
    BR0280I BRBACKUP time stamp: 2008-11-14 22.20.47
    BR0308I Shutdown of database instance <MYSID> successful
    BR0280I BRBACKUP time stamp: 2008-11-14 22.20.47
    BR0229I Calling backup utility with function 'backup'...
    BR0278I Command output of '/usr/sap/<MYSID>/SYS/exe/run/backint -u <MYSID> -f backup -i /oracle/<MYSID>/sapbackup/.bdzgizji.lst -t file -p /oracle/<MYSID>/102_64/dbs/init<MYSID>.utl -c':
    WARNING: sort_backup_type not specified in .utl file
    WARNING: default sort_backup_type to <size> for backup
    ///Here i feel some doubt initially but it does not have to take anything with this error as same warning is there in DEV server log also but there backup is sucessful///
    Program:          /usr/sap/<MYSID>/SYS/exe/run/backint 6.0
    Input File:          /oracle/<MYSID>/sapbackup/.bdzgizji.lst
    Profile:          /oracle/<MYSID>/102_64/dbs/init<MYSID>.utl
    Function:          BACKUP
    Backup Type:          BACKUP_FILE
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata1/sr3_1/sr3.data1
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata1/sr3_2/sr3.data2
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata1/sr3_3/sr3.data3
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata1/sr3_4/sr3.data4
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata1/sr3_5/sr3.data5
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata2/sr3_10/sr3.data10
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata2/sr3_6/sr3.data6
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata2/sr3_7/sr3.data7
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata2/sr3_8/sr3.data8
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata2/sr3_9/sr3.data9
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata3/sr3_11/sr3.data11
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata3/sr3_12/sr3.data12
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata3/sr3_13/sr3.data13
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata3/sr3_14/sr3.data14
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata3/sr3_15/sr3.data15
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata4/sr3_16/sr3.data16
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata4/sr3_17/sr3.data17
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata4/sr3_18/sr3.data18
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata4/sr3_19/sr3.data19
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata4/sr3_20/sr3.data20
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata1/sr3700_1/sr3700.data1
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata1/sr3700_2/sr3700.data2
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata1/sr3700_3/sr3700.data3
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata1/sr3700_4/sr3700.data4
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata2/sr3700_5/sr3700.data5
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata2/sr3700_6/sr3700.data6
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata2/sr3700_7/sr3700.data7
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata2/sr3700_8/sr3700.data8
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata3/sr3700_10/sr3700.data10
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata3/sr3700_11/sr3700.data11
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata3/sr3700_12/sr3700.data12
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata3/sr3700_9/sr3700.data9
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata4/sr3700_13/sr3700.data13
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata4/sr3700_14/sr3700.data14
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata4/sr3700_15/sr3700.data15
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata4/sr3700_16/sr3700.data16
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata4/sr3700_17/sr3700.data17
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata4/sr3700_18/sr3700.data18
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata4/sr3700_19/sr3700.data19
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata1/sr3usr_1/sr3usr.data1
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata2/temp_1/temp.data1
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata3/undo_1/undo.data1
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata1/sysaux_1/sysaux.data1
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata1/sysaux_2/sysaux.data2
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata1/system_1/system.data1
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/sapdata1/system_2/system.data2
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/origlogA/log_g11m1.dbf
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/origlogB/log_g12m1.dbf
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/origlogA/log_g13m1.dbf
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/origlogB/log_g14m1.dbf
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    #FILE..... /oracle/<MYSID>/origlogA/cntrl/cntrl<MYSID>.dbf
    #SAVED.... VXF1226681408
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.02
    BR0232I 51 of 51 files saved by backup utility
    BR0230I Backup utility called successfully
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.04
    BR0304I Starting and opening database instance <MYSID> ...
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.35
    BR0305I Start and open of database instance <MYSID> successful
    BR0117I ARCHIVE LOG LIST after backup for database instance <MYSID>
    Parameter                      Value
    Database log mode              Archive Mode
    Automatic archival             Enabled
    Archive destination            /oracle/<MYSID>/oraarch/<MYSID>arch
    Archive format                 %t_%s_%r.dbf
    Oldest online log sequence     2864
    Next log sequence to archive   2867
    Current log sequence           2867             SCN: 21991272
    Database block size            8192             Thread: 1
    Current system change number   22012086         ResetId: 665869765
    BR0280I BRBACKUP time stamp: 2008-11-15 05.11.37
    BR0229I Calling backup utility with function 'backup'...
    BR0278I Command output of '/usr/sap/<MYSID>/SYS/exe/run/backint -u <MYSID> -f backup -i /oracle/<MYSID>/sapbackup/.bdzgizji.lst -t file -p /oracle/<MYSID>/102_64/dbs/init<MYSID>.utl -c':
    WARNING: sort_backup_type not specified in .utl file
    WARNING: default sort_backup_type to <size> for backup
    Program:          /usr/sap/<MYSID>/SYS/exe/run/backint 6.0
    Input File:          /oracle/<MYSID>/sapbackup/.bdzgizji.lst
    Profile:          /oracle/<MYSID>/102_64/dbs/init<MYSID>.utl
    Function:          BACKUP
    Backup Type:          BACKUP_FILE
    BR0280I BRBACKUP time stamp: 2008-11-15 05.12.09
    #PFLOG.... /oracle/<MYSID>/102_64/dbs/init<MYSID>.ora
    #SAVED.... VXF1226706058
    BR0280I BRBACKUP time stamp: 2008-11-15 05.12.09
    #PFLOG.... /oracle/<MYSID>/102_64/dbs/spfile<MYSID>.ora
    #SAVED.... VXF1226706058
    BR0280I BRBACKUP time stamp: 2008-11-15 05.12.09
    #PFLOG.... /oracle/<MYSID>/102_64/dbs/init<MYSID>.sap
    #SAVED.... VXF1226706058
    BR0280I BRBACKUP time stamp: 2008-11-15 05.12.09
    #PFLOG.... /oracle/<MYSID>/102_64/dbs/init<MYSID>.utl
    #SAVED.... VXF1226706058
    BR0280I BRBACKUP time stamp: 2008-11-15 05.12.09
    #PFLOG.... /oracle/<MYSID>/sapreorg/space<MYSID>.log
    #SAVED.... VXF1226706058
    BR0280I BRBACKUP time stamp: 2008-11-15 05.12.09
    #PFLOG.... /oracle/<MYSID>/sapreorg/struc<MYSID>.log
    #SAVED.... VXF1226706058
    BR0280I BRBACKUP time stamp: 2008-11-15 05.12.09
    #PFLOG.... /oracle/<MYSID>/sapbackup/bdzgizji.aff
    #SAVED.... VXF1226706058
    BR0280I BRBACKUP time stamp: 2008-11-15 05.12.09
    #PFLOG.... /oracle/<MYSID>/sapbackup/back<MYSID>.log
    #SAVED.... VXF1226706058
    BR0280I BRBACKUP time stamp: 2008-11-15 05.12.09
    BR0232I 8 of 8 files saved by backup utility
    BR0230I Backup utility called successfully
    BR0056I End of database backup: bdzgizji.aff 2008-11-15 05.12.09
    BR0280I BRBACKUP time stamp: 2008-11-15 05.12.13
    BR0053I BRBACKUP completed successfully with warnings
    BR0280I BRBACKUP time stamp: 2008-11-15 05.12.13
    BR0291I BRARCHIVE will be started with options '-U -d util_file -sd -c'
    BR0280I BRBACKUP time stamp: 2008-11-15 05.13.36
    BR0292I Execution of BRARCHIVE finished with return code 0
    Please suggest as i am not able to understand that error code.
    Thanks

  • Imp full db successful with warnings

    Looking for options to fix those , or can i ignore them? What would be side effect if i drop/cascade users and re-run imp after increasing tablespace TS_PUBLIC size or i should not do that? and just fix the little warnings or even just ignore them?
    Most of tables (i would say 95% ) & there data imported successfully after full imp , db size is 80GB around, import terminated successfully with warnings , which are below.....
    IMP-00017: following statement failed with ORACLE error 1659:
    "CREATE TABLE "CA_QUERY_1"
    "ABLESPACE "TS_PUBLIC""
    IMP-00041: Warning: object created with compilation warnings
    "CREATE FORCE VIEW "ADMIN"."CHECK_EXTENTS_V"
    IMP-00041: Warning: object created with compilation warnings
    "CREATE TRIGGER MT1758.MEDDRA_MT1758_THE_SYN_UPD"

    DBA2011 wrote:
    Looking for options to fix those , or can i ignore them? What would be side effect if i drop/cascade users and re-run imp after increasing tablespace TS_PUBLIC size or i should not do that? and just fix the little warnings or even just ignore them?
    Most of tables (i would say 95% ) & there data imported successfully after full imp , db size is 80GB around, import terminated successfully with warnings , which are below.....
    IMP-00017: following statement failed with ORACLE error 1659:
    "CREATE TABLE "CA_QUERY_1"
    "ABLESPACE "TS_PUBLIC""
    IMP-00041: Warning: object created with compilation warnings
    "CREATE FORCE VIEW "ADMIN"."CHECK_EXTENTS_V"
    IMP-00041: Warning: object created with compilation warnings
    "CREATE TRIGGER MT1758.MEDDRA_MT1758_THE_SYN_UPD"; I would suggest you to look at export log and find out which are the tables that got failed and import only those tables again. Since the size is quite high as you said.
    Secondly, since 95% tables are already import, so i suggest you to increase the Tablespace size by adding datafile or extending existing one, then run the import for rest 5% tables.
    Third, You said can you ignore warning? During import oracle tries to create Views, it first check if the tables from which view is being create are already exists or not. If the tables doesn't exists oracle will create view forcefully, and mark these view as invalid. The only way to make the views valid is to alter the views definition to point to the correct base tables.
    So there is little activity left after import is done with warning, that you have to alter the view definitions so that correct tables can be used.
    Also see MOS -> IMP-00041 ORA-04063 FROMUSER/TOUSER IMPORT INTO NEW DATABASE [ID 1059520.6]
    Hope my suggestions helps you

  • Export terminated successfully with warnings.

    Hi,
    I have a 9i database (9.2.0.8.0) running on a HP Unix machine (B.11.11). The database size is 170GB.
    When I run a full database export, I get couple of ORA-01403 error.
    EXP-00008: ORACLE error 1403 encountered
    ORA-01403: no data found
    But the end of it, it shows Export terminated successfully with warnings.
    Is my export backup valid or do I need to solve the ORA-01403 issue? And how do I solve that?
    Request your quick help on this1
    thanks!

    I checked the Oracle Support notes, but it says that the cause is due to the FILESIZE parameter. But we have not used the FILESIZE parameter in our environment.
    And there are enough space in the file system too. So I dont think the spacing is an issue here.
    userid=dba_backup/xxxxxx
    file=xxxxxx.dmp
    compress=n
    consistent=y
    full=y
    rows=y
    direct=yThe solution mentioned in the note is:
    Solution
    -- To implement the solution, please execute the following steps::
    Add more files to the file= list to make sure there is enough space available for the export.How do I do that? file=xxxxxx.dmp, yyyyyy.dmp is it?
    Thanks!

  • How to fix ORA-01658 error message

    Am trying to get a old bit of database code working and am getting the following errors with the following
    REM **********************************************************************
    CREATE TABLE gam_service ( /*gam_ser*/
    service_group_id NUMBER(10) NOT NULL
      CONSTRAINT gam_ser_fk_gam_sergrp REFERENCES gam_service_group (service_group_id)
      ON DELETE CASCADE,
    service_id NUMBER(10) NOT NULL,
    service_name VARCHAR2(127) NOT NULL, /*length from GICS code*/
    service_type CHAR(1) NOT NULL, /* Service type Gulp, socKet mp, Special client*/
    server VARCHAR2(127) NOT NULL, /* Server name, e.g. "gulp" */
    version VARCHAR2(20) NOT NULL, /*Required version number of server binary*/
    parameters VARCHAR2(2000) NULL, /* parameters to start the service - could be binary */
    cpu_power_level NUMBER(3) NULL,     /* NULL for wildcard*/
    os_type CHAR(1) NULL      /* NULL for wildcard (Solaris2.4, winNt)*/
      CONSTRAINT gam_ser_ostype CHECK (os_type IN (NULL, 'S', 'N')),
    hardware_owner_type VARCHAR2(10) NULL  /* NULL for wildcard (company name)*/
    )  TABLESPACE gam_tab STORAGE (INITIAL 25K NEXT 100K PCTINCREASE 100 MINEXTENTS 1 MAXEXTENTS unlimited)
    CREATE UNIQUE INDEX gam_service_pk on gam_service (service_group_id, service_name)
    TABLESPACE gam_ind
    STORAGE (INITIAL 5K NEXT 20K PCTINCREASE 100 MINEXTENTS 1 MAXEXTENTS unlimited)
    CREATE SEQUENCE gam_service_seq
      INCREMENT BY 1
      START WITH 1001
      NOCYCLE
      NOCACHE
      NOORDER
    here the error message
    CREATE UNIQUE INDEX gam_service_pk on gam_service (service_group_id, service_name)
    ERROR at line 1:
    ORA-01658: unable to create INITIAL extent for segment in tablespace GAM_IND
    i really hope some one can help me thanks

    You just ran out of space in gam_ind tablespace. Contiguous space to be precise. Your INTITIAL extend needs 5K of contoguous space. And since you specified PCTINCREASE 100, need for contiguous space will double with each next extent. So most likely you ended up with a case where there is plenty of free space not no contiguous space of required size.
    SY.

  • HTMLDB Newbie: ORA-01658 error when creating new app or table from sprdsht

    Hey there. I'm new to HTML DB and trying to create a new app (or even a new table) from a simple spreadsheet. I've tried both comma and tab delimited, but get the same error message every time. This is in my workspace on htmldb.oracle.com.
    "ORA-20001: create_table error: ORA-20001: Excel load run ddl error: ORA-01658: unable to create INITIAL extent for segment in tablespace FLOW_693"

    Scott,
    Thanks, but I don't think that's the problem. My workspace is 100Mb, and it's almost empty. I can install & run sample apps just fine, but not create a new app from a spreadsheet. The spreadsheet is small, to: nine columns and about 50 rows.
    Any ideas?

  • DB12 log RC code:0001 Success with warnings

    Hi,
    I have scheduled <b>Whole database online + redo log backup</b> , which started successfully. I have went to DB12 then log shows that return code :0001 sucess with warnings
    Also message pops up that "The redo log files created during the last online backup have not yet been archived using BRARCHIVE.They are needed for a complete recovery."
    Not sure what is this warning. Any help...
    Thanks
    Chimsik

    How are you scheduling this backup (in DB13 or using scripts / sapdba)? Please post the part of the backup log that shows the command that was run to start the backups. Also please post from the end of the logs, which shows progress in backing up the archives. There may also be a separate archive log file corresponding to your backup run. Please paste that as well.
    Typically archives can be covered by flags -sd, -cds etc. I would like to know what flags your backup is using.
    Regards,
    Sanket

  • Owb beta 3 / master detail mapping with sequence ora-00936 error

    I'm not able to use sequence operator in mapping to create relationships between different record type from the same flat file. I have got an sql error ORA-00936: expression absente
    The problem seem to be the sequence is not referenced in the sql loader parameter. The sequence exists, was deployed sucessfully, the mapping is validated and successfully deployed. The problem occurs during execution

    Good afternoon "micwic",
    In general, mappings with flat files make use of data generators, not sequence operators. This is what the User Guide (10gR1 but I guess R2 works similar) says for the Data Generator Operator :
    Use a Data Generator operator to provide information such as record number, system date, and sequence values.
    For mappings with flat file sources, the Data Generator operator also provides a place to enter constant information. For mappings with Flat File sources and targets, the Data Generator operator connects the mapping to SQL*Loader to generate the data stored in the database record.
    The following functions are available:
    RECNUM
    SYSDATE
    SEQUENCE
    It is possible for Warehouse Builder to generate data by specifying only sequences, record numbers, system dates, and constants as field specifications. SQL*Loader inserts as many records as are specified by the LOAD keyword.
    Setting a Column to the Data File Record Number
    Use the RECNUM keyword to set an attribute to the number of the records that tthe record was loaded from. Records are counted sequentially from the beginning of the first data file, starting with record 1. RECNUM increments as each logical record is assembled. It increments for records that are discarded, skipped, rejected, or loaded.
    For example, if you use the option SKIP=10, the first record loaded has a RECNUM of 11.
    Setting a Column to the Current Date
    A column specified with SYSDATE gets the current system date, as defined by the SQL language SYSDATE function.
    The target column must be of type CHAR or DATE. If the column is of type CHAR, then the date is loaded in the format dd-mon-yy. After the load, you only access it in that format. If the system date is loaded into a DATE column, then you can only access it in a variety of formats including the time and the date. A new system date/time is used for each array of records inserted in a conventional path load and for each block of records loaded during a direct path load.
    Setting a Column to a Unique Sequence Number
    The SEQUENCE keyword ensures a unique value for a column. SEQUENCE increments for each record that is loaded or rejected. It does not increment for records that are discarded or skipped.
    Recommendation: For PL/SQL mappings use a Constant Operator or Mapping Sequence Operator instead of a Data Generator.
    etc.
    Good luck, Patrick

  • Creating a view using With causes ORA-00600 Error

    Hello Ladies and Gents,
    I've been trying to deploy a recursive query as a view in Oracle XE and Standard Edition, neither to much success.
    The query is located in this question here: http://stackoverflow.com/questions/17358109/how-to-retrieve-all-recursive-children-of-parent-row-in-oracle-sq
    with recursion_view(base, parent_id, child_id, qty) as (
       -- first step, get rows to start with
       select
      parent_id base,
      parent_id,
      child_id,
      qty
      from
      md_boms
      union all
      -- subsequent steps
      select
       -- retain base value from previous level
      previous_level.base,
       -- get information from current level
      current_level.parent_id,
      current_level.child_id,
       -- accumulate sum
       (previous_level.qty + current_level.qty) as qty
      from
      recursion_view previous_level,
      md_boms current_level
      where
      current_level.parent_id = previous_level.child_id
    select
      base, parent_id, child_id, qty
    from
      recursion_view
    order by
      base, parent_id, child_id
    The query itself works and returns results. However, when I try to create a view with that query, I receive errors.
    I've posted two screenshots: http://www.williverstravels.com/JDev/Forums/StackOverflow/17358109/ViewError.jpg and http://www.williverstravels.com/JDev/Forums/StackOverflow/17358109/InternalError.jpg The first one with the ! and * is when I am using JDeveloper 11g, using the Database Navigator, right-click on View and select "New View". I receive the error when I click OK. I can indeed create the view through a sql script, but when I attempt to view the data, I receive the ORA_00600 error.
    I've tried this on both my local machine for XE (version 11.2.0.2.0) and on 11g Standard Edition (11.2.0.2.v6) via Amazon Web Services. The result is the same.
    Does anyone know how to get around this?

    Not 5 minutes after I post this, I decide not to use JDev's graphical editor, and simply write
    SELECT * FROM BOMS_VIEW;
    And it works like a charm.  I just can't use data tab to view the records in the editor.  Wish I had known that 5 hours ago.

  • Traport importing problem with repeating return code error 8

    Hi all,
    We are facing some transport import problem.When we sent transport initially AAA900244,they faced with return code error 8 and syntax error 109.As the information provided by the client,one of the include  program which is not availble at client system that was included in this transport.So that was the problem.Again we have taken  new  tranport AAA900247 without this include program then same type of error message they faced with return code error 8 and syntax error 109 in the include program when imported.
    I have one doubt, when importing new transport this should overwrite the earlier transport data.Why the same type error client is getting.What might be the reason.
    Is earlier transport  imported?? Why it throwing same type error.What actually the fuctionality of Return code 8 whether it is imported or discarded.
    Thanks in advance.
    Regards.....Balu

    Hi Ramesh,
    That include is not at all required at client system.So next time when we have taken transport we have not included this include program.They imported new transport without this include program.But they are facing same error as they faced first time. What could be reason??
    Regards...Balu

  • Export terminated successfully with warnings, warning is ignoreable

    Is this waring ignorable?
    Connected to: Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.4.0 - Production
    Export done in US7ASCII character set and AL16UTF16 NCHAR character set
    server uses WE8ISO8859P1 character set (possible charset conversion)
    Note: table data (rows) will not be exported
    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-00097: Object type "SYSTEM"."ValidateTravelBookingRS102_T" is not in a valid state, type will not be exported
    "q17alsn.log" 622 lines, 32848 characters
    EXP-00097: Object type "SYSTEM"."ErrorType100_T" is not in a valid state, type will not be exported
    EXP-00097: Object type "SYSTEM"."TravelSegmentType99_T" is not in a valid state, type will not be exported
    EXP-00097: Object type "SYSTEM"."Address98_T" is not in a valid state, type will not be exported
    EXP-00097: Object type "SYSTEM"."ValidateTravelBookingRQ96_T" is not in a valid state, type will not be exported
    EXP-00097: Object type "SYSTEM"."TravelSegmentType95_T" is not in a valid state, type will not be exported
    EXP-00097: Object type "SYSTEM"."Address94_T" is not in a valid state, type will not be exported
    EXP-00097: Object type "SYSTEM"."ValidateTravelPlanRS92_T" is not in a valid state, type will not be exported
    EXP-00097: Object type "SYSTEM"."ErrorType90_T" is not in a valid state, type will not be exported
    EXP-00097: Object type "SYSTEM"."TravelSegmentType89_T" is not in a valid state, type will not be exported
    EXP-00097: Object type "SYSTEM"."TravelSegmentType87_T" is not in a valid state, type will not be exported
    EXP-00097: Object type "SYSTEM"."MemberInfoRS85_T" is not in a valid state, type will not be exported
    EXP-00097: Object type "SYSTEM"."ErrorType83_T" is not in a valid state, type will not be exported
    EXP-00097: Object type "SYSTEM"."MemberInfoRQ81_T" is not in a valid state, type will not be exported
    . exporting system procedural objects and actions
    . exporting pre-schema procedural objects and actions
    . exporting cluster definitions
    . about to export SYSTEM's tables via Direct Path ...
    . . exporting table AQ$_INTERNET_AGENTS

    The object type"s status is invalid which may be caused by a dependant type"s modification without cascading the change. You must have the type recompiled using ALTER TYPE COMPILE prior to performing the export operation.
    ~ Madrid

  • [Q] ORA-30510 error while doing full database import

    We have ORACLE 9.2.0.6 on Redhat LINUX AS 3.4. while we doing "full database import" there has ORA-30510 come out. I searched Metalink and Google, but not found much information. The error messages on import are:
    . importing OUTLN's objects into OUTLN
    . importing SYSTEM's objects into SYSTEM
    . importing TKOWNER's objects into TKOWNER
    IMP-00017: following statement failed with ORACLE error 30510:
    "CREATE TRIGGER "TKOWNER".TRIG_DONOTANALYZE before analyze on schema decla"
    "re begin if sys.dictionary_obj_name = 'MYWTKEMPLOYEE' then raise_ap"
    "plication_error(-20101, 'Do Not ANALYZE MYWTKEMPLOYEE'); end if; end; "
    IMP-00003: ORACLE error 30510 encountered
    ORA-30510: system triggers cannot be defined on the schema of SYS user
    . importing SYS's objects into SYS
    . importing TKOWNER's objects into TKOWNER
    About to enable constraints...
    Import terminated successfully with warnings.

    877410 wrote:
    Hi I get the following ierrors while importing a schema from prod to dev database... can anyone help ,thanks!
    impdp system DIRECTORY=DATA_PUMP_DIR DUMPFILE=abcdprod.DMP LOGFILE=abcdprod.log REMAP_SCHEMA=abcdprod:abcddev
    ORA-39002: invalid operation
    ORA-31694: master table "SYSTEM"."SYS_IMPORT_FULL_01" failed to load/unload
    ORA-31644: unable to position to block number 170452 in dump file "/ots/oracle/echo/wxyz/datapump/abcdprod.DMPpost complete command line for the expdp that made the abcdprod.DMP file

  • ORA-12699: error when connecting to server with FIPS enabled

    Hi all,
    I have a oracle client and server with FIPS enabled on them. When I use SQL Developer from the client, I can connect to the server and run queries on them.
    I have an ADO based application, which I am trying to run on the client to query the oracle server, but the open database call seems to fail on this with the ORA-12699 error ..
    Heres the connection string I am using ... "Provider=OraOLEDB.Oracle;Data Source=Test;User Id=scott;Password=tiger;"
    Are there any other options to be added to the connection string string ?? any ideas / comments would be of great help ...
    Note : I am using Oracle 11G ..
    --sachi                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

    Naveen,
    Forms 5.0 is not certified and not tested with Oracle DB 10g because it was desupported before 10g got released.
    The other problem is hard to give a generic answer for and I suggest to address this to metalink.oracle.com
    Frank

  • Import fails with unable to extend table CUSTOM.CASA_TRAN_HIST_UPLD by 6999

    Hi,
    I have taken export backup of table from 9.2.0.4 on AIX & trying to import in 11.1.0.7.0 on AIX
    while importing im getting the following error.
    ORA-01653: unable to extend table CUSTOM.CASA_TRAN_HIST_UPLD by 699912 in tablespace CUSTOM
    As the table size is 37G , total free space in tablespace is 40G,
    & no index on the table.
    following are sum lines from import file
    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
    Export file created by EXPORT:V09.02.00 via direct path
    import done in US7ASCII character set and UTF8 NCHAR character set
    import server uses AL32UTF8 character set (possible charset conversion)
    export server uses AL16UTF16 NCHAR character set (possible ncharset conversion)
    . importing DATAMIG's objects into CUSTOM
    . . importing table "CASA_TRAN_HIST_UPLD"
    IMP-00058: ORACLE error 1653 encountered
    ORA-01653: unable to extend table CUSTOM.CASA_TRAN_HIST_UPLD by 699912 in tablespace CUSTOM
    IMP-00028: partial import of previous table rolled back: 62844421 rows rolled back
    IMP-00017: following statement failed with ORACLE error 1917:
    "GRANT SELECT ON "CASA_TRAN_HIST_UPLD" TO "BSGUSER""
    IMP-00003: ORACLE error 1917 encountered
    ORA-01917: user or role 'BSGUSER' does not exist
    Import terminated successfully with warnings.
    is there any to resolve the issue.
    how to change NCHAR set for import.
    Thanks

    Hello,
    which & how i can set character set for import.About the Character Set, it's a setting at the Database creation. You may check it by using the following query on the Source and Target Databases:
    select * from v$nls_parameters; The NLS_CHARACTERSET will give you the Character set of the Database.
    It cannot be changed easily. It may imply a Database creation and export/import of data ( see Note *225912.1* ).
    Else, when you export (with the Original Export/Import utility) it's recommended to set the NLS_LANG parameter.
    The NLS_LANG parameter has 3 components:
    - Language
    - Territory
    - Client Character Set
    A wrong setting of the NLS_LANG may lead to conversion. However starting with *9i* most data is exported with the Character Set of the Database regardless the NLS_LANG setting. The following note may give you some details about it:
    Export/Import and NLS Considerations [ID 15095.1]Hope this help.
    Best regards,
    Jean-Valentin

Maybe you are looking for