Exclude create user statements using datapump API

I’m trying to perform a schema import and exclude the "create user" statements using the datapump API but I can’t get the syntax correct for the dbms_datapump.metadata_filter call.
Using impdp I use a parfile that includes the following statements:
schemas=bob, john
exclude=user
How do I achieve the same effect using the dbms_datapump.metadata_filter API?
Any assistance greatly appreciated.
Gavin

Did you ever figure out your issue? I'm having the same issue after I try to set attributes.

Similar Messages

  • Finding create user statement using the export dump

    I have an Oracle export dump and it is a schema level export only.
    Is there any way that I can get the create user statement from that dump using import full=y show=y ?
    How do I identify the create user statement once I did the show=y

    Yes with full export this is possible because full export will create all schemas but this is not possible with schema level export because schema level import does not recreate schema.

  • Stats Not getting imported while importing partition using DATAPUMP API

    Hi,
    I am using datapump API for exporting a partition of a table and the importing the partition into table on another DB.
    The data is getting imported but i could the partition stats are not getting imported. I am using TABLE_EXISTS_ACTION = APPEND.
    any idea on how to achieve the stats also to be imported into the partition.
    Thanks!

    Hi,
    I am using datapump API for exporting a partition of a table and the importing the partition into table on another DB.
    The data is getting imported but i could the partition stats are not getting imported. I am using TABLE_EXISTS_ACTION = APPEND.
    any idea on how to achieve the stats also to be imported into the partition.
    Thanks!

  • "The CREATE USER statement must be the only statement in the batch" in SQL Azure - why? what to do?

    I'm getting an error on a line in the middle of a larger sql script, only in SQL Azure.
    IF NOT EXISTS (SELECT * FROM sys.database_principals WHERE name = N'foouser')
    CREATE USER [foouser] FOR LOGIN [foouser] WITH DEFAULT_SCHEMA=[dbo]
    GO
    Error: "The CREATE USER statement must be the only statement in the batch."
    I don't actually understand what 'the only statement in the batch' means.
    What is a batch? Is it a SQL file? Is it related to a 'GO' statement or an 'IF' statement? What is the reason for the error? And how do I avoid it?
    Thanks,
    Tim

    >IF...ELSE imposes conditions on the execution of a Transact-SQL statement
    I understand the general purpose of an If statement. I could let go of our definition of statement counting disagreeing too except that because of the error I'm stuck.
    It's less important for Create User but what I am really puzzled over now is a very similar issue how am I supposed to do a safe version of CREATE LOGIN, when I don't know whether a login has been previously created on the server or whether I
    am setting up the database on a clean server?
    IF NOT EXISTS (SELECT * FROM sys.server_principals WHERE name = N'foouser')
    CREATE LOGIN [foouser] WITH PASSWORD = 'asdfasdf'
    GO
    If I try and execute this script, it throws the same error as above.
    The first unworkable workaround idea is to omit the if statement
    CREATE LOGIN [foouser] WITH PASSWORD = 'asdfasdf'
    GO
    But if the login already exists on the server (because a similar script was already run), then the script throws an error.
    The second unworkable workaround idea is to do
    DROP LOGIN [foouser]
    GO
    CREATE LOGIN [foouser] WITH PASSWORD = 'asdfasdf'
    GO
    Obviously this throws an error in the second block if the login doesn't already exist on the server.
    The third workaround idea I have is to go conditional by putting an IF condition around DROP instead of CREATE:
    Unfortunately that doesn't work for me either!
    "The DROP LOGIN statement must be the only statement in the batch"
    (This is despite the fact that 'drop login' is listed on the
    supported commands page, not the partially supported page..?! Which disagrees with the notes on
    this page.)
    Anyway the real question I am interesting in addressing is: is there actually a way to have a 'Create/Delete login
    if exists' operation which is SQL-Azure compatible and doesn't throw me error messages (which messes with the sql execution tool I am using)?
    If there is no way, I would like to believe it's because it would be a bad idea to do this. But in that case why is it a bad idea?
    Tim

  • Create user statement on Procedures

    Hi,
    How to use create user command in oracle procedure.
    Whenever I am using the statemet create user <username> identified by <password> it gives me the error. But whenever I am removing this statement the procedure is compiling successfully.
    Is there anyway to use create user statement inside procedure?
    Regards,
    Indraneel

    You have to use dynamic sql :
    SQL> begin
      2  execute immediate ('create user test_user identified by test_user');
      3  end;
      4  /
    PL/SQL procedure successfully completed.
    SQL>Of course the command should be completed with other information (e.g. default tablespace, temporary tablespace, and so on).
    Paul

  • Creating a mapping using the API

    Hi Brian, I am curious about this use case - what's the reason you are looking to do it using the API? You can create several objects using the API and the most typical use case we have observed is where mapping developers create a pattern or what we call as a "template" - which is a mapping with various properties parameterized. For example you can create a mapping with the filter parameterized, or define a very generic mapping with source, target and the field map between those all parameterized. Once you do that, you can create a "task" for this mapping (known as Mapping Configuration Task) - that can be done using our UI or using our REST API. If you choose the latter, you can pass on parameter values as part of the API request. Suggest you to take a look at our new Developer Portal, and specifically at the sections Templates and REST API there. Feel free to post any further questions here. If you sign up to the developer program there, you will get much more direct help.https://community.informatica.com/community/technology_partner_network Amol

    I was wondering about creating a mapping using the API. It clearly states in the Dev guide that this is possible, but when I perform a get mapping request, I don't see all the information given for a certain object.  For example, I don't see an expression in the mapping object (although one exists when I view the object in Cloud).   Has anyone else done this? Is it easy to create objects via the API?  Thanks!

  • Returning error while listing  reportees of a user by using worklist api.

    Hi,
    I am trying to list reportees of a user by using bpel worklist APi in custom application.the following is the code fragment of that:
    BPMUser bpmUser = gu.getWorkflowServiceClient().getAuthorizationService("dm.hoogly").lookupUser(gu.getWorkflowServiceClient().getTaskQueryService().getWorkflowContext("dm.hoogly").getUser());
    List directs = bpmUser.getReportees(1);
    System.out.println(" size..."+directs.size());
    its retuning error.
    Can any one help me how to list a reportees of a user by using BPELworklist api
    thanks
    Murali

    Hi..
    I am using 10.1.3.3 SOA suite.
    thanks
    Murali

  • How to create RMA lines using OE_ORDER_PUB API

    Hi All,
    We are trying to create RMA lines using OE_ORDER_PUB API but every time API creating <b>Standard Order Line</b> line type in application.
    My program is creating order header as a <b>Return Order</b>, i am passing corrent line type ids (1028 - RMA Shipment, 1027 - RMA Receipt) but oracle API is creating Standard Order Lines (ID 1001).
    Can any one tell me about that?
    Thanks
    Ravi
    null

    Check the defaulting rules setup. Defaulting rule will derive the line type based on the order type and shippable flag etc.
    Also check the line flows assigned to the order type in transaction types window.
    Thanks / Bhaskar Akkala

  • Blank lines in create user statement

    Hi everyone,
    DataModeler still has problems with blank lines in statements. My "create user" statements look like
    CREATE USER HTTPUSR
    IDENTIFIED BY httpusr
    DEFAULT TABLESPACE HTTP_BIG
    TEMPORARY TABLESPACE TEMP
    QUOTA UNLIMITED ON HTTP_BIG
    QUOTA UNLIMITED ON HTTP_LOG
    QUOTA UNLIMITED ON HTTP_SMALL
    ACCOUNT LOCK
    and fail. I have to remove the blank lines manually.
    Is this a known bug or a new one?

    Bug 14248076 resolved for DM 3.1.2.704 and DM 3.2.0.720

  • Creating user's objective through API ot working

    I am making use of the HR_OBJECTIVES_API API to create objective for users. to test the API, I run the small script below. It create a new row in the per_objective table but the HRMS interface fail to recognize it. It does not appear in the scorecard of the user. What am I missing?
    /* Auto Generation of Script Start */
    DECLARE
         -- Start of Variable declarations, Initialize Variables with appropriate values to test the script
         -- VARCHAR2 size is set to 2000 by default, please enter target table name to retrieve the exact limit
         -- Input Variables
         V_VALIDATE                      BOOLEAN:=false;
         V_EFFECTIVE_DATE                DATE := trunc(sysdate);
         V_BUSINESS_GROUP_ID             NUMBER:=81;
         V_NAME                          VARCHAR2(2000):='Just a Second test from TOAD';
         V_START_DATE                    DATE:=trunc(sysdate);
         V_OWNING_PERSON_ID              NUMBER:=264;
         V_TARGET_DATE                   DATE;
         V_ACHIEVEMENT_DATE              DATE;
         V_DETAIL                        VARCHAR2(2000);
         V_COMMENTS                      VARCHAR2(2000);
         V_SUCCESS_CRITERIA              VARCHAR2(2000);
         V_APPRAISAL_ID                  NUMBER;
         V_ATTRIBUTE_CATEGORY            VARCHAR2(2000);
         V_ATTRIBUTE1                    VARCHAR2(2000);
         V_ATTRIBUTE2                    VARCHAR2(2000);
         V_ATTRIBUTE3                    VARCHAR2(2000);
         V_ATTRIBUTE4                    VARCHAR2(2000);
         V_ATTRIBUTE5                    VARCHAR2(2000);
         V_ATTRIBUTE6                    VARCHAR2(2000);
         V_ATTRIBUTE7                    VARCHAR2(2000);
         V_ATTRIBUTE8                    VARCHAR2(2000);
         V_ATTRIBUTE9                    VARCHAR2(2000);
         V_ATTRIBUTE10                   VARCHAR2(2000);
         V_ATTRIBUTE11                   VARCHAR2(2000);
         V_ATTRIBUTE12                   VARCHAR2(2000);
         V_ATTRIBUTE13                   VARCHAR2(2000);
         V_ATTRIBUTE14                   VARCHAR2(2000);
         V_ATTRIBUTE15                   VARCHAR2(2000);
         V_ATTRIBUTE16                   VARCHAR2(2000);
         V_ATTRIBUTE17                   VARCHAR2(2000);
         V_ATTRIBUTE18                   VARCHAR2(2000);
         V_ATTRIBUTE19                   VARCHAR2(2000);
         V_ATTRIBUTE20                   VARCHAR2(2000);
         V_ATTRIBUTE21                   VARCHAR2(2000);
         V_ATTRIBUTE22                   VARCHAR2(2000);
         V_ATTRIBUTE23                   VARCHAR2(2000);
         V_ATTRIBUTE24                   VARCHAR2(2000);
         V_ATTRIBUTE25                   VARCHAR2(2000);
         V_ATTRIBUTE26                   VARCHAR2(2000);
         V_ATTRIBUTE27                   VARCHAR2(2000);
         V_ATTRIBUTE28                   VARCHAR2(2000);
         V_ATTRIBUTE29                   VARCHAR2(2000);
         V_ATTRIBUTE30                   VARCHAR2(2000);
         V_SCORECARD_ID                  NUMBER:=9193;
         V_COPIED_FROM_LIBRARY_ID        NUMBER;
         V_COPIED_FROM_OBJECTIVE_ID      NUMBER;
         V_ALIGNED_WITH_OBJECTIVE_ID     NUMBER;
         V_NEXT_REVIEW_DATE              DATE;
         V_GROUP_CODE                    VARCHAR2(2000);
         V_PRIORITY_CODE                 VARCHAR2(2000);
         V_APPRAISE_FLAG                 VARCHAR2(2000):='Y';
         V_VERIFIED_FLAG                 VARCHAR2(2000);
         V_TARGET_VALUE                  NUMBER;
         V_ACTUAL_VALUE                  NUMBER;
         V_WEIGHTING_PERCENT             NUMBER;
         V_COMPLETE_PERCENT              NUMBER;
         V_UOM_CODE                      VARCHAR2(2000);
         V_MEASUREMENT_STYLE_CODE        VARCHAR2(2000):='N_M';
         V_MEASURE_NAME                  VARCHAR2(2000);
         V_MEASURE_TYPE_CODE             VARCHAR2(2000);
         V_MEASURE_COMMENTS              VARCHAR2(2000);
         V_SHARING_ACCESS_CODE           VARCHAR2(2000);
         -- Output Variables
         V_WEIGHTING_OVER_100_WARNING    BOOLEAN;
         V_WEIGHTING_APPRAISAL_WARNING   BOOLEAN;
         V_OBJECTIVE_ID                  NUMBER;
         V_OBJECT_VERSION_NUMBER         NUMBER;
    BEGIN
        DBMS_output.enable(800000);
         --  Calling API HR_OBJECTIVES_API.CREATE_OBJECTIVE
         HR_OBJECTIVES_API.CREATE_OBJECTIVE(P_VALIDATE                     => V_VALIDATE
                                           ,P_EFFECTIVE_DATE               => V_EFFECTIVE_DATE
                                           ,P_BUSINESS_GROUP_ID            => V_BUSINESS_GROUP_ID
                                           ,P_NAME                         => V_NAME
                                           ,P_START_DATE                   => V_START_DATE
                                           ,P_OWNING_PERSON_ID             => V_OWNING_PERSON_ID
                                           ,P_TARGET_DATE                  => V_TARGET_DATE
                                           ,P_ACHIEVEMENT_DATE             => V_ACHIEVEMENT_DATE
                                           ,P_DETAIL                       => V_DETAIL
                                           ,P_COMMENTS                     => V_COMMENTS
                                           ,P_SUCCESS_CRITERIA             => V_SUCCESS_CRITERIA
                                           ,P_APPRAISAL_ID                 => V_APPRAISAL_ID
                                           ,P_ATTRIBUTE_CATEGORY           => V_ATTRIBUTE_CATEGORY
                                           ,P_ATTRIBUTE1                   => V_ATTRIBUTE1
                                           ,P_ATTRIBUTE2                   => V_ATTRIBUTE2
                                           ,P_ATTRIBUTE3                   => V_ATTRIBUTE3
                                           ,P_ATTRIBUTE4                   => V_ATTRIBUTE4
                                           ,P_ATTRIBUTE5                   => V_ATTRIBUTE5
                                           ,P_ATTRIBUTE6                   => V_ATTRIBUTE6
                                           ,P_ATTRIBUTE7                   => V_ATTRIBUTE7
                                           ,P_ATTRIBUTE8                   => V_ATTRIBUTE8
                                           ,P_ATTRIBUTE9                   => V_ATTRIBUTE9
                                           ,P_ATTRIBUTE10                  => V_ATTRIBUTE10
                                           ,P_ATTRIBUTE11                  => V_ATTRIBUTE11
                                           ,P_ATTRIBUTE12                  => V_ATTRIBUTE12
                                           ,P_ATTRIBUTE13                  => V_ATTRIBUTE13
                                           ,P_ATTRIBUTE14                  => V_ATTRIBUTE14
                                           ,P_ATTRIBUTE15                  => V_ATTRIBUTE15
                                           ,P_ATTRIBUTE16                  => V_ATTRIBUTE16
                                           ,P_ATTRIBUTE17                  => V_ATTRIBUTE17
                                           ,P_ATTRIBUTE18                  => V_ATTRIBUTE18
                                           ,P_ATTRIBUTE19                  => V_ATTRIBUTE19
                                           ,P_ATTRIBUTE20                  => V_ATTRIBUTE20
                                           ,P_ATTRIBUTE21                  => V_ATTRIBUTE21
                                           ,P_ATTRIBUTE22                  => V_ATTRIBUTE22
                                           ,P_ATTRIBUTE23                  => V_ATTRIBUTE23
                                           ,P_ATTRIBUTE24                  => V_ATTRIBUTE24
                                           ,P_ATTRIBUTE25                  => V_ATTRIBUTE25
                                           ,P_ATTRIBUTE26                  => V_ATTRIBUTE26
                                           ,P_ATTRIBUTE27                  => V_ATTRIBUTE27
                                           ,P_ATTRIBUTE28                  => V_ATTRIBUTE28
                                           ,P_ATTRIBUTE29                  => V_ATTRIBUTE29
                                           ,P_ATTRIBUTE30                  => V_ATTRIBUTE30
                                           ,P_SCORECARD_ID                 => V_SCORECARD_ID
                                           ,P_COPIED_FROM_LIBRARY_ID       => V_COPIED_FROM_LIBRARY_ID
                                           ,P_COPIED_FROM_OBJECTIVE_ID     => V_COPIED_FROM_OBJECTIVE_ID
                                           ,P_ALIGNED_WITH_OBJECTIVE_ID    => V_ALIGNED_WITH_OBJECTIVE_ID
                                           ,P_NEXT_REVIEW_DATE             => V_NEXT_REVIEW_DATE
                                           ,P_GROUP_CODE                   => V_GROUP_CODE
                                           ,P_PRIORITY_CODE                => V_PRIORITY_CODE
                                           ,P_APPRAISE_FLAG                => V_APPRAISE_FLAG
                                           ,P_VERIFIED_FLAG                => V_VERIFIED_FLAG
                                           ,P_TARGET_VALUE                 => V_TARGET_VALUE
                                           ,P_ACTUAL_VALUE                 => V_ACTUAL_VALUE
                                           ,P_WEIGHTING_PERCENT            => V_WEIGHTING_PERCENT
                                           ,P_COMPLETE_PERCENT             => V_COMPLETE_PERCENT
                                           ,P_UOM_CODE                     => V_UOM_CODE
                                           ,P_MEASUREMENT_STYLE_CODE       => V_MEASUREMENT_STYLE_CODE
                                           ,P_MEASURE_NAME                 => V_MEASURE_NAME
                                           ,P_MEASURE_TYPE_CODE            => V_MEASURE_TYPE_CODE
                                           ,P_MEASURE_COMMENTS             => V_MEASURE_COMMENTS
                                           ,P_SHARING_ACCESS_CODE          => V_SHARING_ACCESS_CODE
                                           ,P_WEIGHTING_OVER_100_WARNING   => V_WEIGHTING_OVER_100_WARNING
                                           ,P_WEIGHTING_APPRAISAL_WARNING  => V_WEIGHTING_APPRAISAL_WARNING
                                           ,P_OBJECTIVE_ID                 => V_OBJECTIVE_ID
                                           ,P_OBJECT_VERSION_NUMBER        => V_OBJECT_VERSION_NUMBER
    dbms_output.put_line('Successfully created objective: ' || v_objective_id ||
         ' for TARGET PERSON_ID: ' || v_owning_person_id );
    exception when others then
         dbms_output.put_line('error : ' || sqlerrm);
    END;

    Hi,
           Can you just try by giving effective date and start date as some previous date rather than sysdate?
    Regards,
    Vinod

  • GetSelectedFields()  for time stamp and user stamp using java api

    using Java API's
    getSelectedFields() returns NULL  value if values presented also, for Time stamp and User stamp
    properties in Flat tables , is there any other alternative way to get the SelectedFields values ?
    Edited by: Vijaya Sekhar Reddy Alla on Mar 19, 2008 3:16 PM

    Well, I can't say I solved the problem, because I got another one afterwards.
    As usually I created a GetFieldListCommand, set its needed attributes and executed it. Then I read all the field properties out:
    FieldProperties[] fieldProp = getFieldListCommand.getFields();
    Afterwards it is possible to do what you want. Using a for-loop.
    for (FieldProperties fp : fieldProperties) {
        UserStampFieldProperties usfp = (UserStampFieldProperties) fp; // <= Cast error
        FieldId[] fieldIDs = usfp.getSelectedFields();
    And this is what I get now:
    Exception in thread "main" java.lang.ClassCastException: com.sap.mdm.schema.fields.FixedWidthTextFieldProperties cannot be cast to com.sap.mdm.schema.fields.UserStampFieldProperties
    Why this happens, I don't know. But it should somehow be solveable.

  • INDEX failed to create while  Import using datapump

    Hi DBA's
    database 11.2.01
    OS : Solaris 10
    I am trying to Import the data using the following command.
    impdp system/******* SCHEMAS=EIMS DIRECTORY=expdp_dir DUMPFILE=eimsexp.dmp*
    but it fails import index and error out, but the tables and data imported.
    I checked in the metalink and followed the Note id (During Data Pump Import Index Creation Fails With: ORA-39083 and ORA-14102 errors OR ORA-39083 ORA-02158 and ORA-39112 errors [ID 1066635.1]) , but no luck.
    Kindly advice me.
    ERROR
    ORA-39083: Object type INDEX failed to create with error:
    ORA-14102: only one LOGGING or NOLOGGING clause may be specified
    Failing sql is:
    CREATE UNIQUE INDEX "EIMS"."PK_MDS_PSTN_LEVEL" ON "EIMS"."MDS_PSTN_LEVEL" ("REGION_CODE", "AREA_CODE", "LEVEL_NO", "EXCHANGE_CODE") PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING NOCOMPRESS LOGGING STORAGE( INITIAL 65536 FREELISTS 1 FREELIST GROUPS 1) TABLESPACE "EIMS_DATA" PARALLEL 1
    ORA-39083: Object type INDEX failed to create with error:
    ORA-14102: only one LOGGING or NOLOGGING clause may be specified
    Best Regards,
    SG

    Dear Hussein,
    Yes i applied the patch, still i am getting the same error and again i followed one more note (Impdp Failed With Error Ora-39083, 0ra-01403 On Index_statistics (Doc ID 755253.1))
    in that note i given option "exclude=index", then i got in different error.
    We are in the process of doing testing on Tablespace Encryption.
    We are having two instances one is dev and uat instance.
    we are creating Encryption tablespace on uat instance and trying to import the data from dev instance only from particular user.
    We completed the followings.
    1. Created tablespace Encryption.
    2. Created user and assigned the tablespace to the user EIMS1.
    3. Took export from the dev instance using the following command.
    expdp system/******** SCHEMAS=EIMS DIRECTORY=expdp_dir DUMPFILE=eimsexp.dmp
    4. Importing data from
    impdp system/******** REMAP_SCHEMA=EIMS:EIMS1 DIRECTORY=expdp_dir exclude=index DUMPFILE=eimsexp.dmp
    Error
    ====
    ORA-39083: Object type CONSTRAINT failed to create with error:
    ORA-14102: only one LOGGING or NOLOGGING clause may be specified
    Failing sql is:
    ALTER TABLE "EIMS1"."DOCS" ADD PRIMARY KEY ("ID") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING NOCOMPRESS LOGGING STORAGE( INITIAL 65536 FREELISTS 1 FREELIST GROUPS 1) TABLESPACE "EIMS_DATA" ENABLE
    ORA-39083: Object type CONSTRAINT failed to create with error:
    ORA-14102: only one LOGGING or NOLOGGING clause may be specified
    before i used to get the bellow errors
    ==========================
    ALTER TABLE "EIMS1"."TST1" ADD CONSTRAINT "ADMACHINEDEPLOYMENTSTATUS_PK" PRIMARY KEY ("MID") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING NOCOMPRESS LOGGING STORAGE( INITIAL 65536 FREELISTS 1 FREELIST GROUPS 1) TABLESPACE "EIMS_DATA" ENABLE
    Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
    ORA-39083: Object type INDEX_STATISTICS failed to create with error:
    ORA-01403: no data found
    ORA-01403: no data found
    Failing sql is:
    DECLARE I_N VARCHAR2(60); I_O VARCHAR2(60); c DBMS_METADATA.T_VAR_COLL; df varchar2(21) := 'YYYY-MM-DD:HH24:MI:SS'; BEGIN DELETE FROM "SYS"."IMPDP_STATS"; c(1) := 'ID'; DBMS_METADATA.GET_STAT_INDNAME('EIMS1','DOCS',c,1,i_o,i_n); INSERT INTO "SYS"."IMPDP_STATS" (type,version,flags,c1,c2,c3,c5,n1,n2,n3,n4,n5,n6,n7,n8,n9,n10,n11,n12,d1,cl1) VALUES ('I',5,0,I_N,NUL
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MDS_PSTN_LEVEL" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_AMT_REQUEST_PRIORITY" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_AMT_REQUEST_QUEUE" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_BH02_REQUEST_PRIORITY" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_BH03_REQUEST_PRIORITY" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_BH03_REQUEST_QUEUE" creation failed
    ORA-39112: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"EIMS1"."PK_MD_BH04_REQUEST_PRIORITY" creation failed
    Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
    Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 1049 error(s) at 20:43:02
    Thanks
    SG

  • Creating User ID using BAPI_USER_CREATE

    Hi
    I am creating a user ID using the BAPI_USER_CREATE.
    I couldnt find the parameter in this to add roles to the user.
    Can anyone let me know How to assign roles to the users created by using this BAPI.
    Regards,
    Osman Jabri

    Hi,
    identity management API is one of the best documented APIs I've ever seen. Here is an official [documentation|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/668e6629-0701-0010-7ca0-994cb7dec5a3?overridelayout=true].
    Cheers

  • Creating Job material using public API from WIP

    Take the entered component part number and search in the WIP job material requirements. This should use a WIP API. If the material is found, increment the quantity. If material is not found, create the job material using public API. (Provide WIP API details)
    The java object, oracle.apps.csd.schema.server .CsdHvWipJobPvtEO is a wrapper to call WIP API. This should be used to create material requirements is this the procedure to create job material Req.
    from OAF how we have to create Job material transaction

    Hi Pat,
    What is your SBO version? I've seen several cases in which the login/connection procedure (both in the client and via DI API) has become much slower after upgrading to SBO 2005.
    Do you experience the same slowness when connecting via DI API in a non-WebService setting?
    I would not recommend using DI API in a web service context in the first place. DI Server would give you a much more robust, stable and scalable infrastructure to build upon.
    Henry

  • Issue in creating sales order using process_header API

    Hi all,
    We have a requirement to create sales order using apps adapter in ebiz from SOA suite composite.I used OE_ORDER_PUB.Process_header API to create order header.
    When I pass the inputs and test the service,I get output with return_status='S'. But no record falls at the OE_ORDER_HEADER_ALL table.
    I cant identify where the problem is.Pls suggest me with the things to resolve this issue.
    Thanks,
    goutham

    Hi all,
    We have a requirement to create sales order using apps adapter in ebiz from SOA suite composite.I used OE_ORDER_PUB.Process_header API to create order header.
    When I pass the inputs and test the service,I get output with return_status='S'. But no record falls at the OE_ORDER_HEADER_ALL table.
    I cant identify where the problem is.Pls suggest me with the things to resolve this issue.
    Thanks,
    goutham

Maybe you are looking for