Excluding certain tables with import

Hello,
I would like to know if there is any way to exclude certain tables when performing an Oracle import. We have certain tables which do not need to be imported, and would significantly help space if some tables could be excluded. Thanks.

Hi,
Well, a workaround is to fake the oracle import utility by precreate a not right table which you don't want import.
Example, I want import all objects from scott to other schema toto, except the emp table. You know the emp's scott table:
TOTO@DEMO102> conn scott/demo102
Connected.
SCOTT@DEMO102> desc emp
Name                                      Null?    Type
EMPNO                                     NOT NULL NUMBER(4)
ENAME                                              VARCHAR2(10)
JOB                                                VARCHAR2(9)
MGR                                                NUMBER(4)
HIREDATE                                           DATE
SAL                                                NUMBER(7,2)
COMM                                               NUMBER(7,2)
DEPTNO                                             NUMBER(2)I have duplicate into emp2 which won't exclude :
SCOTT@DEMO102> desc emp2
Name                                      Null?    Type
EMPNO                                              NUMBER(4)
ENAME                                              VARCHAR2(10)
JOB                                                VARCHAR2(9)
MGR                                                NUMBER(4)
HIREDATE                                           DATE
COMM                                               NUMBER(7,2)
DEPTNO                                             NUMBER(2)
SCOTT@DEMO102> Well, as toto, I create a table emp with other structure :
SYSTEM@DEMO102> conn toto/toto
Connected.
TOTO@DEMO102> desc emp
ERROR:
ORA-04043: object emp does not exist
TOTO@DEMO102> create table emp (col1 number);
Table created.
TOTO@DEMO102> desc emp
Name                                      Null?    Type
COL1                                               NUMBERAt this point, I export the scott's schema :
E:\oracle\ora102\BIN>exp system/demo102 owner=scott file=e:\files\expscott.dmp log=e:\files\expscott.log
Export: Release 10.2.0.2.0 - Production on Wed Sep 20 20:50:14 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
About to export specified users ...
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user SCOTT
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions for user SCOTT
About to export SCOTT's objects ...
. exporting database links
. exporting sequence numbers
. exporting cluster definitions
. about to export SCOTT's tables via Conventional Path ...
. . exporting table                              A          2 rows exported
. . exporting table                              B          4 rows exported
. . exporting table                          BONUS          0 rows exported
. . exporting table                              C          0 rows exported
. . exporting table                         CARLES      40811 rows exported
. . exporting table                        CECILIA          2 rows exported
. . exporting table                        CUBITTM         25 rows exported
. . exporting table                           DATA          4 rows exported
. . exporting table                           DEPT          4 rows exported
. . exporting table                            DIM          2 rows exported
. . exporting table EMP 14 rows exported
. . exporting table EMP2 14 rows exported
. . exporting table                        WORKERS          1 rows exported
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting referential integrity constraints
. exporting triggers
. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
. exporting materialized views
. exporting snapshot logs
. exporting job queues
. exporting refresh groups and children
. exporting dimensions
. exporting post-schema procedural objects and actions
. exporting statistics
Export terminated successfully without warnings.
E:\oracle\ora102\BIN>Then import with ignore=y :
E:\oracle\ora102\BIN>imp system/demo102 fromuser=scott touser=toto file=e:\files
\expscott.dmp log=e:\files\imp_to_toto.log ignore=yHere the log result :
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
Export file created by EXPORT:V10.02.01 via conventional path
import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
. importing SCOTT's objects into TOTO
. . importing table                            "A"          2 rows imported
. . importing table                            "B"          4 rows imported
. . importing table                        "BONUS"          0 rows imported
. . importing table                            "C"          0 rows imported
. . importing table                       "CARLES"      40811 rows imported
. . importing table                      "CECILIA"          2 rows imported
. . importing table                      "CUBITTM"         25 rows imported
. . importing table                         "DATA"          4 rows imported
. . importing table                         "DEPT"          4 rows imported
. . importing table                          "DIM"          2 rows imported
. . importing table "EMP"
IMP-00058: ORACLE error 904 encountered
ORA-00904: "DEPTNO": invalid identifier
IMP-00017: following statement failed with ORACLE error 904:
ORA-06512: at line 1
. . importing table "EMP2" 14 rows imported
. . importing table                        "EMP25"         14 rows imported
. . importing table                         "EMP3"          0 rows imported
. . importing table                         "EMP6"         14 rows imported
. . importing table                      "WORKERS"          1 rows imported
IMP-00041: Warning: object created with compilation warnings
"CREATE FORCE VIEW "TOTO"."VW_EMP2"                            ("EMPNO","ENA"
"ME","JOB","MGR","HIREDATE","SAL","COMM","DEPTNO","TMS2") AS "
"select "EMPNO","ENAME","JOB","MGR","HIREDATE","SAL","COMM","DEPTNO","TMS2" "
"from emp2"
IMP-00017: following statement failed with ORACLE error 904:
"ALTER TABLE "EMP" ADD CONSTRAINT "FK_DEPTNO" FOREIGN KEY ("DEPTNO") REFEREN"
"CES "DEPT" ("DEPTNO") ENABLE NOVALIDATE"
IMP-00003: ORACLE error 904 encountered
ORA-00904: "DEPTNO": invalid identifier
IMP-00017: following statement failed with ORACLE error 1031:
"CREATE SNAPSHOT "MV1" USING ("MV1", (8, 'DEMO102.REGRESS.RDBMS.DEV.US.ORACL"
"E.COM', 1, 0, 0, "SCOTT", "EMP", '2006-04-24:23:28:56', 0, 51151, '2006-04-"
"24:23:28:56', '', 0, 1171373, 0, NULL), 2097472, 8, ('2006-04-24:23:28:56',"
" 22, 0, 0, 1171373, 0, 0, 2, NULL, NULL)) REFRESH FORCE AS"
"select cast(empno-7000 as number(3)) empno, sal from emp"
IMP-00003: ORACLE error 1031 encountered
ORA-01031: insufficient privileges
IMP-00017: following statement failed with ORACLE error 12003:
"ALTER SNAPSHOT "MV1" COMPILE"
IMP-00003: ORACLE error 12003 encountered
ORA-12003: materialized view "TOTO"."MV1" does not exist
About to enable constraints...
Import terminated successfully with warnings.Note that all assowiated objects were in error, but table emp was not import.
SCOTT@DEMO102> conn toto/toto
Connected.
TOTO@DEMO102> desc emp
Name                                      Null?    Type
COL1                                               NUMBER
TOTO@DEMO102> select * from emp;
no rows selected
TOTO@DEMO102> select * from emp2;
     EMPNO ENAME      JOB              MGR HIREDATE       COMM     DEPTNO
      7369 SMITH      CLERK           7902 17/12/80                    20
      7499 ALLEN      SALESMAN        7698 20/02/81        300         30
      7521 WARD       SALESMAN        7698 22/02/81        500         30
      7566 JONES      MANAGER         7839 02/04/81                    20
      7654 MARTIN     SALESMAN        7698 28/09/81       1400         30
      7698 BLAKE      MANAGER         7839 01/05/81                    30
      7782 CLARK      MANAGER         7839 09/06/81                    10
      7788 SCOTT      ANALYST         7566 19/04/87                    20
      7839 KING       PRESIDENT            17/11/81                    10
      7844 TURNER     SALESMAN        7698 08/09/81          0         30
      7876 ADAMS      CLERK           7788 23/05/87                    20
      7900 JAMES      CLERK           7698 03/12/81                    30
      7902 FORD       ANALYST         7566 03/12/81                    20
      7934 MILLER     CLERK           7782 23/01/82                    10
14 rows selected.
TOTO@DEMO102> If I drop emp table, and re-import, emp table will be import as well.
Nicolas.

Similar Messages

Internal table with Import and Export

Hi All,
Hi all
Please let me know the use of <b>Internal table with Import and Export parameters and SET/GET parameters</b>, on what type of cases we can use these? Plese give me the syntax with some examples.
Please give me detailed analysis on the above.
Regards,
Prabhu

Hi Prabhakar,
There are three types of memories.
1. ABAP MEMORY
2. SAP MEMORY
3. EXTERNAL MEMORY.
1.we will use EXPORT/ IMPORT TO/ FROM MEMORY-ID when we want to transfer between ABAP memory
2. we will use GET PARAMETER ID/ SET PARAMETER ID to transfer between SAP MEMORY
3. we will use EXPORT/IMPORT TO/FROM SHARED BUFFER to transfer between external memory.
ABAP MEMORY : we can say that two reports in the same session will be in ABAP MEMORY
SAP MEMORY: TWO DIFFERENT SESSIONS WILL BE IN SAP MEMORY.
for ex: IF WE CALL TWO DIFFERENT TRANSACTIONS SE38, SE11
then they both are in SAP MEMORY.
EXTERNAL MEMORY: TWO different logons will be in EXTERNAL MEMORY.
<b>Syntax</b>
To fill the input fields of a called transaction with data from the calling program, you can use the SPA/GPA technique. SPA/GPA parameters are values that the system stores in the global, user-specific SAP memory. SAP memory allows you to pass values between programs. A user can access the values stored in the SAP memory during one terminal session for all parallel sessions. Each SPA/GPA parameter is identified by a 20-character code. You can maintain them in the Repository Browser in the ABAP Workbench. The values in SPA/GPA parameters are user-specific.
ABAP programs can access the parameters using the SET PARAMETER and GET PARAMETER statements.
To fill one, use:
SET PARAMETER ID <pid> FIELD <f>.
This statement saves the contents of field <f> under the ID <pid> in the SAP memory. The code <pid> can be up to 20 characters long. If there was already a value stored under <pid>, this statement overwrites it. If the ID <pid> does not exist, double-click <pid> in the ABAP Editor to create a new parameter object.
To read an SPA/GPA parameter, use:
GET PARAMETER ID <pid> FIELD <f>.
This statement fills the value stored under the ID <pid> into the variable <f>. If the system does not find a value for <pid> in the SAP memory, it sets SY-SUBRC to 4, otherwise to 0.
To fill the initial screen of a program using SPA/GPA parameters, you normally only need the SET PARAMETER statement.
The relevant fields must each be linked to an SPA/GPA parameter.
On a selection screen, you link fields to parameters using the MEMORY ID addition in the PARAMETERS or SELECT-OPTIONS statement. If you specify an SPA/GPA parameter ID when you declare a parameter or selection option, the corresponding input field is linked to that input field.
On a screen, you link fields to parameters in the Screen Painter. When you define the field attributes of an input field, you can enter the name of an SPA/GPA parameter in the Parameter ID field in the screen attributes. The SET parameter and GET parameter checkboxes allow you to specify whether the field should be filled from the corresponding SPA/GPA parameter in the PBO event, and whether the SPA/GPA parameter should be filled with the value from the screen in the PAI event.
When an input field is linked to an SPA/GPA parameter, it is initialized with the current value of the parameter each time the screen is displayed. This is the reason why fields on screens in the R/3 System often already contain values when you call them more than once.
When you call programs, you can use SPA/GPA parameters with no additional programming overhead if, for example, you need to fill obligatory fields on the initial screen of the called program. The system simply transfers the values from the parameters into the input fields of the called program.
However, you can control the contents of the parameters from your program by using the SET PARAMETER statement before the actual program call. This technique is particularly useful if you want to skip the initial screen of the called program and that screen contains obligatory fields.
Reading Data Objects from Memory
To read data objects from ABAP memory into an ABAP program, use the following statement:
Syntax
IMPORT <f1> [TO <g 1>] <f 2> [TO <g 2>] ... FROM MEMORY ID <key>.
This statement reads the data objects specified in the list from a cluster in memory. If you do not use the TO <g i > option, the data object <f i > in memory is assigned to the data object in the program with the same name. If you do use the option, the data object <f i > is read from memory into the field <g i >. The name <key> identifies the cluster in memory. It may be up to 32 characters long.
You do not have to read all of the objects stored under a particular name <key>. You can restrict the number of objects by specifying their names. If the memory does not contain any objects under the name <key>, SY-SUBRC is set to 4. If, on the other hand, there is a data cluster in memory with the name <key>, SY-SUBRC is always 0, regardless of whether it contained the data object <f i >. If the cluster does not contain the data object <f i >, the target field remains unchanged.
Saving Data Objects in Memory
To read data objects from an ABAP program into ABAP memory, use the following statement:
Syntax
EXPORT <f1> [FROM <g 1>] <f 2> [FROM <g 2>] ... TO MEMORY ID <key>.
This statement stores the data objects specified in the list as a cluster in memory. If you do not use the option FROM <f i >, the data object <f i > is saved under its own name. If you use the FROM <g i > option, the data objet <g i > is saved under the name <f i >. The name <key> identifies the cluster in memory. It may be up to 32 characters long.
Check this link.
http://www.sap-img.com/abap/difference-between-sap-and-abap-memory.htm
Thanks,
Susmitha.
Reward points for helpful answers.

How to Create new database (copy all table with data excluding 2 table )with existing database.

Please follow the scenario:
using C#
1) current database file name is DB20122013.
when user click on new year button
2)Create backup copy of current database
3)New database should create with all table(excluding table "Dailytemp" and "DailyMain") with data and database name as DB20132014.
Musakkhir Sayyed.

Hi,
I hope, below stored procedure is useful for your scenario.
CREATE PROC Create_New_Database
( @DBNAME VARCHAR(550)
)AS
Test : Exec [Create_New_Database] @DBNAME='DB20122013'
BEGIN TRY
SET NOCOUNT ON
DECLARE @sql VARCHAR(MAX), @DBNAME_NEW VARCHAR(550),@num int
IF EXISTS(SELECT 1 FROM sys.databases WHERE name=@DBNAME) AND ISNUMERIC(RIGHT(@DBNAME,4))=1
BEGIN
SELECT @num= RIGHT(@DBNAME,4)
SELECT @DBNAME_NEW='DB'+CAST(@num AS VARCHAR(10))+''+CAST(@num+1 AS VARCHAR(10))
IF EXISTS(SELECT 1 FROM sys.databases WHERE name=@DBNAME_NEW)
BEGIN
SELECT @DBNAME_NEW+' database already exists'
END
ELSE
BEGIN
SET @sql='USE '+@DBNAME+' '+' backup database '+@DBNAME+' to disk = ''C:\'+@DBNAME+'.bak'' '
+' restore database '+@DBNAME_NEW+' from disk = ''C:\'+@DBNAME+'.bak'''
+' with move '''+@DBNAME+''' to ''C:\'+@DBNAME+'_data.mdf'' ,
move '''+@DBNAME+'_log'' to ''C:\'+@DBNAME+'_log.log'''
EXEC (@sql)
SET @sql=''
SET @sql=' USE '+@DBNAME_NEW+' IF EXISTS(SELECT 1 FROM SYS.TABLES WHERE NAME=''Dailytemp'')
BEGIN DROP TABLE Dailytemp END IF EXISTS(SELECT 1 FROM SYS.TABLES WHERE NAME=''DailyMain'')
BEGIN DROP TABLE DailyMain END '
EXEC (@sql)
END
END
ELSE
BEGIN
SELECT 'Database is now found or Database name does not mach the scenario'
END
SET NOCOUNT OFF
END TRY
BEGIN CATCH
DECLARE @ErrorMessage NVARCHAR(4000)
DECLARE @ErrorSeverity INT
DECLARE @ErrorState INT
SELECT @ErrorMessage = ERROR_MESSAGE(), @ErrorSeverity = ERROR_SEVERITY(),@ErrorState = ERROR_STATE()
RAISERROR (@ErrorMessage,@ErrorSeverity,@ErrorState )
END CATCH;
GO
Regards,
RAMBHARATH

Exclude mlog$ table during import

Hi Experts,
Could you please help me on how to exclude the materialized view log tables (mlog$ table) during data pump import.
Error:
ORA-31693: Table data object "RM_DBA"."MLOG$_ACTUAL_INCOME" failed to load/unload and is being skipped due to error:
Regards,
Boris

I found the answer here..
impdp job_name=schemaexp1 schemas=sthomas dumpfile=exp_schem.dmp logfile=imp_schema.log directory=exp_dir EXCLUDE=table:\"like \'MLOG\$\%\'\",MATERIALIZED_VIEW_LOG,MATERIALIZED_VIEW
Original Post: http://www.acehints.com/2013/09/how-to-exclude-mlog-materialized-view.html

Normal Import - Exclude tables form import

Hi ,
Is it possible to exclude all tables from a database dump import.I have a very big size dump.I dont want to import the tables.Just anted to check some procedures/packages/triggers.
is there any way to do this.
Thanks in Advance,
SSN

You have 2 options:
1) As suggested above, use the SHOW=Y option of import and you can see everything in the log file generated.
2) Create a database, run the import with rows=N and you would be able to access all the structures.

Error while importing a table with BLOB column

Hi,
I am having a table with BLOB column. When I export such a table it gets exported correctly, but when I import the same in different schema having different tablespace it throws error
IMP-00017: following statement failed with ORACLE error 959:
"CREATE TABLE "CMM_PARTY_DOC" ("PDOC_DOC_ID" VARCHAR2(10), "PDOC_PTY_ID" VAR"
"CHAR2(10), "PDOC_DOCDTL_ID" VARCHAR2(10), "PDOC_DOC_DESC" VARCHAR2(100), "P"
"DOC_DOC_DTL_DESC" VARCHAR2(100), "PDOC_RCVD_YN" VARCHAR2(1), "PDOC_UPLOAD_D"
"ATA" BLOB, "PDOC_UPD_USER" VARCHAR2(10), "PDOC_UPD_DATE" DATE, "PDOC_CRE_US"
"ER" VARCHAR2(10) NOT NULL ENABLE, "PDOC_CRE_DATE" DATE NOT NULL ENABLE) PC"
"TFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 STORAGE(INITIAL 65536 FREELISTS"
" 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE "TS_AGIMSAPPOLOLIVE030"
"4" LOGGING NOCOMPRESS LOB ("PDOC_UPLOAD_DATA") STORE AS (TABLESPACE "TS_AG"
"IMSAPPOLOLIVE0304" ENABLE STORAGE IN ROW CHUNK 8192 PCTVERSION 10 NOCACHE L"
"OGGING STORAGE(INITIAL 65536 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEF"
"AULT))"
IMP-00003: ORACLE error 959 encountered
ORA-00959: tablespace 'TS_AGIMSAPPOLOLIVE0304' does not exist
I used the import command as follows :
imp <user/pwd@conn> file=<dmpfile.dmp> fromuser=<fromuser> touser=<touser> log=<logfile.log>
What can I do so that this table gets imported correctly?
Also tell me "whether the BLOB is stored in different tablespace than the default tablespace of the user?"
Thanks in advance.

Hello,
U can either
1) create a tablespace with the same name in destination where you are trying to import.
2) get the ddl of the table, modify the tablespace name to reflect the existing tablespace name in destination and run the ddl in the destination database, and run your import command with option ignore=y--> which will ignore all the create errors.
Regards,
Vinay

Help on export sybase iq tables with data and import in another database ?

Help on export Sybase iq 16 tables with data and import into another database ?

Hi Nilesh,
If you have table/index create commands (DDLs), you can create them in Developper and import data using one of methods below
Extract/ Load table
Insert location method : require IQ servers to be entered in interfaces file
Backup/Restore : copy entire database content
If you have not the DDLs, you can generate them using IQ cockpit or SCC.
http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01773.1604/doc/html/san1288042631955.html
http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01840.1604/doc/html/san1281564927196.html
Regards,
Tayeb.

SSIS 2012 is intermittently failing with below "Invalid date format" while importing data from a source table into a Destination table with same exact schema.

We migrated Packages from SSIS 2008 to 2012. The Package is working fine in all the environments except in one of our environment.
SSIS 2012 is intermittently failing with below error while importing data from a source table into a Destination table with same exact schema.
Error: 2014-01-28 15:52:05.19
   Code: 0x80004005
   Source: xxxxxxxx SSIS.Pipeline
   Description: Unspecified error
End Error
Error: 2014-01-28 15:52:05.19
   Code: 0xC0202009
   Source: Process xxxxxx Load TableName [48]
   Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Invalid date format".
End Error
Error: 2014-01-28 15:52:05.19
   Code: 0xC020901C
   Source: Process xxxxxxxx Load TableName [48]
   Description: There was an error with Load TableName.Inputs[OLE DB Destination Input].Columns[Updated] on Load TableName.Inputs[OLE DB Destination Input]. The column status returned was: "Conversion failed because the data value overflowed
the specified type.".
End Error
But when we reorder the column in "Updated" in Destination table, the package is importing data successfully.
This looks like bug to me, Any suggestion?

Hi Mohideen,
Based on my research, the issue might be related to one of the following factors:
Memory pressure. Check there is a memory challenge when the issue occurs. In addition, if the package runs in 32-bit runtime on the specific server, use the 64-bit runtime instead.
A known issue with SQL Native Client. As a workaround, use .NET data provider instead of SNAC.
Hope this helps.
Regards,
Mike Yin
If you have any feedback on our support, please click
here
Mike Yin
TechNet Community Support

Importing a table with a BLOB column is taking too long

I am importing a user schema from 9i (9.2.0.6) database to 10g (10.2.1.0) database. One of the large tables (millions of records) with a BLOB column is taking too long to import (more that 24 hours). I have tried all the tricks I know to speed up the import. Here are some of the setting:
1 - set buffer to 500 Mb
2 - pre-created the table and turned off logging
3 - set indexes=N
4 - set constraints=N
5 - I have 10 online redo logs with 200 MB each
6 - Even turned off logging at the database level with disablelogging = true
It is still taking too long loading the table with the BLOB column. The BLOB field contains PDF files.
For your info:
Computer: Sun v490 with 16 CPUs, solaris 10
memory: 10 Gigabytes
SGA: 4 Gigabytes

Legatti,
I have feedback=10000. However by monitoring the import, I know that its loading average of 130 records per minute. Which is very slow considering that the table contains close to two millions records.
Thanks for your reply.

Problem importing a table with blob's

hi all, I'm facing the following situation.
Source DB : 10.2.0.3 (client's DB)
Destination DB (mine): 10.2.0.4
I've a dump file (traditional) of a particular schema.
I'm running import (imp) to import on my DB.
It runs fine until it reaches one particular table. This table has 6 colums, 3 of them are BLOB.
This table has 260000 rows (checked with export log).
When import reaches row 152352 it stops loading data, but import is still running.
what can I do to get more information from this situation in order to solve this problem?
Any suggestion will be appreciated!
Thanks in advance.

Pl identify the source and target OS versions. Are there any useful messages in the alert.log ? How long did the export take ? Rule of thumb states import will take twice as long. Have you tried expdp/impdp instead ? Also see the following -
How To Diagnose And Troubleshoot Import Or Datapump Import Hung Scenarios          (Doc ID 795034.1)
How To Find The Cause of a Hanging Import Session          (Doc ID 184842.1)
Import is Slow or Hangs          (Doc ID 1037231.6)
Export and Import of Table with LOB Columns (like CLOB and BLOB) has Slow Performance          (Doc ID 281461.1)
HTH
Srini

Import from database an internal table with generic Type : Web Dynpro ABAP

Hi everyone,
i have a requirement in which i'm asked to transfer data flow between two frameworks, from WD Component to another. The problem is that i have to transfer internal tables with generic types. i used the import/ export from database approache but in that way i get an error message saying "Object references and data references not yet supported".
Here is my code to extract a generic internal table from memory.
    DATA l_table_f4 TYPE TABLE OF REF TO data.
FIELD-SYMBOLS: <l_table_f4> TYPE STANDARD TABLE.
DATA lo_componentcontroller TYPE REF TO ig_componentcontroller .
DATA: ls_indx TYPE indx.
lo_componentcontroller =   wd_this->get_componentcontroller_ctr( ).
lo_componentcontroller->fire_vh_search_action_evt( ).
ASSIGN l_table_f4 TO <l_table_f4>.
*-- Import table for Help F4
IMPORT l_table_f4 TO <l_table_f4> FROM DATABASE indx(v1) TO ls_indx ID 'table_help_f4_ID'.
The error message is desplayed when last instruction is executed " IMPORT l_table_f4...".
I saw another post facing the same problem but never solved "Generic Type for import Database".
Please can anyone help ?
Thanks & Kind regards.

hi KIan,
go:
general type
TYPE : BEGIN OF ty_itab,
           field1 TYPE ztab-field1,
           field2 TYPE ztab-field2,
*your own fields here:
           field TYPE i,
           field(30) TYPE c,
           END OF ty_itab.
work area
DATA : gw_itab TYPE ty_itab.
internal table
DATA : gt_itab TYPE TABLE OF ty_itab.
hope this helps
ec

Import of Tables with CLOB problem.

Hi,
I am having problems with the import of tables with CLOB columns.
Tables with CLOB columns will force the use of the tablespace in which it (table) was created originally. It will not be created on the new schema's default tablespace. Is there a way to get around this problem?
More on this problem can be found here :
Re: Import error 1647, CLOB fields problem, need help!
I am using Oracle 9.2.0.6 standard edition, that is why the transportable tablespace option will not work.
Thanx
Rob

Sorry I have posted the wrong link, it should be:
Re: Import error 1647, CLOB fields problem, need help!
Regards
Rob

Import tables with nested table : ORA-00600

In Oracle 9.2
Create object, type as table, and table with nested table (store as syms_ntab) are successfully.
Also its export.
In process of import on another server (also 9.2, 'fromuser=one touser=two') shows errors:
. . importing table "SYMS_NTAB"
IMP-00058: ORACLE error 600 encountered
ORA-00600: internal error code, arguments: [kokeeafi1], [2], [2], [], [], [], [], []
IMP-00075: Warning: The nested table may contain partial rows or duplicate rows
But for all that table is created and error occur on phase inserting strings.
What is this?
In Oracle 8.0.5 i perform similar operation without error.

From Oracle error messages and codes manual:
ORA-00600 internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
Cause: This is the generic internal error number for Oracle program exceptions. It indicates that a process has encountered a low-level, unexpected condition. Causes of this message include:
* timeouts
* file corruption
* failed data checks in memory
* hardware, memory, or I/O errors
* incorrectly restored files
The first argument is the internal message number. Other arguments are various numbers, names, and character strings. The numbers may change meanings between different versions of Oracle.
Action: Report this error to Oracle Support Services after gathering the following information:
* events that led up to the error
* the operations that were attempted that led to the error
* the conditions of the operating system and databases at the time of the error
* any unusual circumstances that occurred before receiving the ORA-00600 message
* contents of any trace files generated by the error
* the relevant portions of the Alter files
Note: The cause of this message may manifest itself as different errors at different times. Be aware of the history of errors that occurred before this internal error.

JCA IConnection call to BAPI with table in table as import and export param

Is it possible to call a BAPI with a table in table as import and export data?
Please give small code example if this is possible.
Thanks in advance.

Inner tables can be handled with:
IRecordSet innerTable = (IRecordSet)outerTable.getObject("INNER_TABLE");

Import table with a different table name!

Dear All,
I have backup all users in my database using exp command.
Now i want to import 2 tables from this backup, as tables already exists i want to import table with different table name.
Is it possible with exp command? If not what else is the solution.
Thanks, Imran

Hi..
Now i want to import 2 tables from this backup, as tables already exists i want to import table with different table name.Is it possible with exp command? If not what else is the solution.
>
Well, its not possible.You can import those two tables in some test database, rename them and then take the export and import in the database you want.
Or,
You can import those 2 tables in some other schema in your database, rename them again take the export and them import it.
Anand

Excluding certain tables with import

Similar Messages

Maybe you are looking for