Unable to Create Term Within a TermSet

Hi,
I am trying to create term inside an existing termset. Following is my code
I am trying to create a term if it doesn't exist in termset. Following is my code
using (SPSite mySite=new SPSite(URL,SPUserToken.SystemUser))
uisng (SPWEb myWeb= mySite.OpenWeb())
TaxonomySession session = new TaxonomySession(myWeb.Site);
TermStore termStore = session.TermStores[TermStoreName];
Group group = termStore.Groups("testGroupName");
//var termSet = group.TermSets["existingTermSet"];
TermSet ts=null;
ts=group.TermSets["existingTermSet"];
int lcid = CultureInfo.CurrentCulture.LCID;
ts.CreateTerm("ABC",lcid);
This throws an error saying "Value cannot be null" in the following line:
ts.CreateTerm("ABC",lcid);
I am really puzzled by this error.
Please suggest me an alternative or root cause so that I can proceed. I am at a loss right now.
I have to use Server Side Object Model and not CSOM

Hi,
 Can you please verify your code with example provided in the below link, it will sure helpful.
http://www.c-sharpcorner.com/UploadFile/54db21/create-term-in-sharepoint-2010-programmatically-using-vs-201/
Regards,
MS

Similar Messages

  • Unable to create a subtask within a task for cProjects

    Hi All,
    I am unable to create a subtask within a task using BAPI_BUS2175_CREATE. When I pass the GUID of the project definition and fill the corresponding task structures to the BAPI, a task gets created at the phase level. But when I pass the GUID of the task along with the task
    information, subtask does not get created. The BAPI returns the following error message:
    DPR_SHARED 051: You cannot create Task for (Task Name).
    Steps for recreating the error message are:
    1. GUID is found out using function module CONVERSION_EXIT_DPRCE_INPUT.
    2. GUID and task information is passed to BAPI_BUS2175_CREATE.
    3. Task is created if project definition GUID is passed, but if task GUID is passed, there is no subtask created. An error message is displayed:
    DPR_SHARED 051: You cannot create Task for (Task Name).
    Any help would be appreciated.
    Thanks,
    Tom

    Hi all,
    I have used the same and it works absolutely fine.
    here is a code sample
    CONSTANTS:
       lc_rfc_none        TYPE string VALUE 'NONE'.       " RFC on same server
    DATA:
      lv_header_task_guid TYPE bapi_ts_guid-parent_guid, " Header Task GUID
      ls_sub_task TYPE bapi_ts_task,
      ls_sub_task_upd TYPE bapi_ts_task_upd,
      lt_crtask_return TYPE TABLE OF bapiret2,
      ls_extension_in TYPE bapiparex,
      ls_extension_out TYPE bapiparex,
      lv_task_guid TYPE bapi_ts_guid-parent_guid. " Task GUID
    * Assign sub-task name. (Task Number is internally generated)
    ls_sub_task-task_name = 'ST 1.1'.
    ls_sub_task_upd-task_name = 'X'.
    * Assign Sort Number
    ls_sub_task-sort_number = '00010'.
    ls_sub_task_upd-sort_number = 'X'.
    * Assign Duration
    ls_sub_task-duration = 30.
    ls_sub_task_upd-duration = 'X'.
    * Assign Work.
    ls_sub_task-planned_work = 240.
    CALL FUNCTION 'CONVERSION_EXIT_CUNIT_INPUT'
      EXPORTING
        input          = 'H'
      IMPORTING
        output         = ls_sub_task-planned_work_unit
      EXCEPTIONS
        unit_not_found = 1
        OTHERS         = 2.
    IF sy-subrc <> 0.
    ENDIF.
    ls_sub_task_upd-planned_work = 'X'.
    ls_sub_task_upd-planned_work_unit = 'X'.
    CALL FUNCTION 'BAPI_BUS2175_CREATE'
         DESTINATION lc_rfc_none
         EXPORTING
             iv_parent_guid   = lv_header_task_guid
             is_task          = ls_sub_task
             is_task_upd      = ls_sub_task_upd
             is_extension_in  = ls_extension_in
          IMPORTING
             es_extension_out = ls_extension_out
         TABLES
             return           = lt_crtask_return.
    * If task is successfully created,
    READ TABLE lt_crtask_return WITH KEY type = lc_success number = '114'.
    IF sy-subrc = 0.
    * Get task GUID
    lv_task_guid = lt_crtask_return-message_v1.
    CALL FUNCTION 'BAPI_CPROJECTS_COMMIT_WORK'
      DESTINATION
        lc_rfc_none
      TABLES
        return = lt_bapiret2.
    endif.
    In order to find the GUID of the header task use function module:
    DPR_GET_GUID_BY_ID_FROM_DB
    with IV_Number  = task number for the header task and IV_OBJECT_TYPE = TTO
    Read the documentation for 'BAPI_BUS2175_CREATE' before using it.
    make sure you have maintained IS_TASK_UPDATE structure as well.
    Regards,
    Reema.

  • [ConfigFwk:390105]Unable to create WLS change list due to a short term automatic lock obtained by user null

    Hi,
    I am getting this error while trying to activate a session in OSB (clustered env with 3 nodes). I have a OSB project which listens to a JMS queue. I was able to create the project fine and was able to activate the session, no issues. But when I tried to update the queue name or delete the project itself, this error gets thrown:
    [ConfigFwk:390105]Unable to create WLS change list due to a short term automatic lock obtained by user null. The user has no pending changes and the lock will expire in 600 seconds. Please try again after the lock has expired.
    Retrying after those seconds takes me back to the same error but the time get's reset to 600 sec.
    I can change the code in that project and activate the session without any issues but if I change any configuration for proxy/business services or delete the project itself, i get this error. the only way to get around this issue is to clone the project and make changes to the cloned project. But, that is not the solution i am looking for as I don't want to keep a old version of the project and don't want to keep creating new queues everytime (since no two proxies can point to the same queue).
    Oh, and this happens only with the projects which deal with JMS queues.
    We are using OSB:
    Oracle Service Bus Version: [Oracle Service Bus 11.1 Sun Dec 18 03:49:34 PST 2011 1447174]
    Oracle Weblogic Server Version: [WebLogic Server 10.3.6.0.10 PSU Patch for BUG19637463 TUE NOV 04 15:54:42 IST 2014]
    Please help.
    Thanks,
    Mukund.

    Hi,
    I am getting this error while trying to activate a session in OSB (clustered env with 3 nodes). I have a OSB project which listens to a JMS queue. I was able to create the project fine and was able to activate the session, no issues. But when I tried to update the queue name or delete the project itself, this error gets thrown:
    [ConfigFwk:390105]Unable to create WLS change list due to a short term automatic lock obtained by user null. The user has no pending changes and the lock will expire in 600 seconds. Please try again after the lock has expired.
    Retrying after those seconds takes me back to the same error but the time get's reset to 600 sec.
    I can change the code in that project and activate the session without any issues but if I change any configuration for proxy/business services or delete the project itself, i get this error. the only way to get around this issue is to clone the project and make changes to the cloned project. But, that is not the solution i am looking for as I don't want to keep a old version of the project and don't want to keep creating new queues everytime (since no two proxies can point to the same queue).
    Oh, and this happens only with the projects which deal with JMS queues.
    We are using OSB:
    Oracle Service Bus Version: [Oracle Service Bus 11.1 Sun Dec 18 03:49:34 PST 2011 1447174]
    Oracle Weblogic Server Version: [WebLogic Server 10.3.6.0.10 PSU Patch for BUG19637463 TUE NOV 04 15:54:42 IST 2014]
    Please help.
    Thanks,
    Mukund.

  • SRM 7.0  Unable to create PO - Classic Scenario.

    Hello,
    We are able to successfully create the below scenario.
    PR in ECC --> Get PR in SRM --> Start Collective processing -> Transfer to Central System (SC is created for the PR @ this time) --> Create RFx --> Rfx Response --> Create PO. (PO is created in ERP, Classic Scenario)
    We are able to get the PR & we are able to create SC successfully and the PR/ SC is available in Sourcing cocpit.
    Able to create RFx --> Rfx Response.
    Now once the RFx Response is Accepted --> We go for creating PO.
    Classic Scenario.
    The error is due to pricing - debugged and checked as mentioned in my earlier message.
    IPC pricing is switched off and the BADI for simple pricing is activated.
    Error :   " Message A BBP_PD 396 cannot be processed in plugin mode HTTP "
    But this is due to pricing is what i guess.
    Error is raised in FM "BBP_PDPRC_UPDATE".
    Kindly Suggest.
    Unable to Create PO
    Regards.
    Edited by: Purshothaman P on Jul 6, 2010 1:50 PM

    Hi,
    Please check and run the following reports (se38): BBP_CND_CUSTOMIZING_CHECK & RSVMCRT_HEALTH_CHECK and post back the results.
    Note for BBP_CND_CUSTOMIZING_CHECK also run 'Simulation of Pricing with Manual Price' (scroll down after executing the report initially).
    Also the badi information you activated tells us a lot. Although i take it that you executed and read everything that's included in the transaction information. The following sentence gives a prety doubtfull feeling for the CPPR scenario to work for your configuration:
    SAP recommends using this BAdI only in exceptional cases and only after checking thoroughly if it is compatible with the Business Scenarios used.
    Note: From what i've just read IPC has to be disabled, certain badi's etc. need to be disabled. And VMC (sap basis) has to be configured. Please view: [http://help.sap.com/SCENARIOS_BUS2008/helpdata/EN/9C/F90B7CB34A4889935D1733C6756D5B/content.htm]
    Could you also please check and provide whether 'normal' SRM classic scenarios like: SC -> PO do run within your system. Also the error and information you have provided is very little.
    Kind regards,
    Tim

  • Unable to create database error

    Hello all-
    I've been working on a project in Robohelp7/HTML for about a
    week. I come in today and try to open my project and receive the
    error "Unable to create database. Check that the directory is not
    read-only.". I've done the obvious of checking the folders and
    files within and they are not marked read only. When I create a new
    project, I receive the same error. I'm stuck at a standstill and
    can't figure out why Robohelp has decided to deny me access to my
    project or the ability to create new ones. I went so far as to
    uninstall and reinstall, to no avail.
    Has anyone encountered this? Any help would be greatly
    appreciated.
    Thanks

    There is a topic on Opening RoboHelp Projects on my site. Rh allows you to browse to either an XPJ or HHP file but that is only as good as the last time you generated an output.
    When you open with an HHP you get an option to use the XPJ or not, in which case one is created. Either way there should be an XPJ. Not sure how you have lost it.
    Backup?
    See www.grainge.org for RoboHelp and Authoring tips
    @petergrainge

  • Unable to create IDOCs after client copy

    I'm unable to create IDOCs after a client copy.  I receive a SAPSQL_ARRAY_INSERT_DUPREC or insert of duplicate rows ABAP dump.
    Does anyone know what how to fix this.  Thank you in advance.
    Runtime Error          SAPSQL_ARRAY_INSERT_DUPREC
    Except.                CX_SY_OPEN_SQL_DB
    Date and Time          22.10.2007 16:50:51
    ShrtText
    The ABAP/4 Open SQL array insert results in duplicate database records.
    What happened?
    Error in ABAP application program.
    The current ABAP program "SAPLEDI1" had to be terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    is especially useful if you want to keep a particular message.
    Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
    neither
    caught nor passed along using a RAISING clause, in the procedure
    "F09_IDOC_INSERT_WITH_NUMBER" "(FORM)"
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    If you use an ABAP/4 Open SQL array insert to insert a record in
    the database and that record already exists with the same key,
    this results in a termination.
    (With an ABAP/4 Open SQL single record insert in the same error
    situation, processing does not terminate, but SY-SUBRC is set to 4.)
    How to correct the error
    Use an ABAP/4 Open SQL array insert only if you are sure that none of
    the records passed already exists in the database.
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "SAPSQL_ARRAY_INSERT_DUPREC" CX_SY_OPEN_SQL_DBC
    "SAPLEDI1" or "LEDI1F09"
    "F09_IDOC_INSERT_WITH_NUMBER"
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
    To obtain this, select in the current display "System->List->
    Save->Local File (unconverted)".
    2. A suitable printout of the system log
    To obtain this, call the system log through transaction SM21.
    Limit the time interval to 10 minutes before and 5 minutes
    after the short dump. In the display, then select the function
    "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, select the Editor function "Further Utilities->
    Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
    or which actions and input led to the error.
    The exception must either be prevented, caught within the procedure
    "F09_IDOC_INSERT_WITH_NUMBER"
    "(FORM)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    System environment
    SAP Release.............. "640"
    Application server....... "auaplxr3q"
    Network address.......... "128.197.135.5"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "000B439ED600"
    Character length......... 8 Bits
    Pointer length........... 64 Bits
    Work process number...... 1
    Short dump setting....... "full"
    Database server.......... "auaplxr3q"
    Database type............ "ORACLE"
    Database name............ "Q63"
    Database owner........... "SAPR3"
    Character set............ "en_US.ISO8859-1"
    SAP kernel............... "640"
    Created on............... "Mar 22 2007 20:48:46"
    Created in............... "AIX 1 5 00538A4A4C00"
    Database version......... "OCI_920 "
    Patch level.............. "175"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
    10.2.0.."
    SAP database version..... "640"
    Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
    Memory usage.............
    Roll..................... 16128
    EM....................... 4189928
    Heap..................... 0
    Page..................... 0
    MM Used.................. 1469352
    MM Free.................. 2718056
    SAP Release.............. "640"
    User and Transaction
    Information on where terminated
    The termination occurred in the ABAP program "SAPLEDI1" in
    "F09_IDOC_INSERT_WITH_NUMBER".
    The main program was "SAPMSSY1 ".
    The termination occurred in line 108 of the source code of the (Include)
    program "LEDI1F09"
    of the source code of program "LEDI1F09" (when calling the editor 1080).
    Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
    the
    procedure "F09_IDOC_INSERT_WITH_NUMBER" "(FORM)" but was not handled locally,
    not declared in the
    RAISING clause of the procedure.
    The procedure is in the program "SAPLEDI1 ". Its source code starts in line 5
    of the (Include) program "LEDI1F09 ".
    Source Code Extract
    Line
    SourceCde
    78
    perform call_badi tables list_container_insert
    79
    using  control
    80
    ident.
    81
    Aufruf des Badi's für das einstreuen neuer Segmente
    82
    perform call_insert_badi tables list_container_insert
    83
    using control
    84
    ident
    85
    changing maxsegnum.
    86
    87
       free list_container_insert
    88
    FREE_RETURN = 1.
    89
    ELSE. " no other IDoc is open in create-mode
    90
    LOOP AT LIST_CONTAINER_CREATE WHERE MANDT EQ SY-MANDT
    91
    AND   DOCNUM EQ IDENT.
    92
    LIST_CONTAINER_CREATE-DOCNUM = DOCNUM.
    93
    MODIFY LIST_CONTAINER_CREATE.
    94
    ADD 1 TO MAXSEGNUM.
    95
    ENDLOOP.
    96
    if control-mestyp eq c_mestyp.
    97
    CALL FUNCTION 'FUNCTION_EXISTS'
    98
    EXPORTING
    99
    funcname           = c_func
    100
    EXCEPTIONS
    101
    FUNCTION_NOT_EXIST = 1.
    102
    IF syst-subrc IS INITIAL.  "Anwendungssystem
    103
    perform call_transform
    104
    tables list_container_create
    105
    using  control.
    106
    ENDIF.
    107
    endif.
    >>>>>
    INSERT EDID4 FROM TABLE LIST_CONTAINER_CREATE.
    109
    Aufruf des Badi's für das Anwendungsmapping einzelner Felder
    110
    perform call_badi tables list_container_create
    111
    using  control
    112
    ident.
    113
    perform call_insert_badi tables list_container_create
    114
    using  control
    115
    ident
    116
    changing maxsegnum.
    117
    118
      free list_container_create
    119
    FREE_RETURN = 0.
    120
    ENDIF.
    121
    122
    insert status records
    123
    124
    SYN_ERROR_IN = ' '.
    125
    CNTR_STATUS = 0.
    126
    REFRESH LIST_STATUS.
    127
    CLEAR LIST_STATUS.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    2
    SY-TABIX
    1
    SY-DBCNT
    1
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    CPIC and RFC Control
    SY-MSGTY
    SY-MSGID
    SY-MSGNO
    000
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    13 FORM         SAPLEDI1                            LEDI1F09                              108
    F09_IDOC_INSERT_WITH_NUMBER
    12 FUNCTION     SAPLEDI1                            LEDI1U19                               33
    EDI_DOCUMENT_CLOSE_CREATE_TAB
    11 FUNCTION     SAPLEDIR                            LEDIRU01                              273
    IDOC_INBOUND_WRITE_TO_DB
    10 FORM         SAPLEDIN                            LEDINF01                              457
    ONE_IDOC_STORE
    9 FUNCTION     SAPLEDIN                            LEDINU05                              234
    IDOC_INBOUND_ASYNCHRONOUS
    8 FORM         SAPLEDIN                            LEDINV05                               19
    IDOC_INBOUND_ASYNCHRONOUS
    7 FORM         SAPMSSY1                            SAPMSSY1                              254
    XAB_RUN_DRIVER
    6 FUNCTION     SAPLSXAB                            LSXABU01                                9
    RFC_RUN_XAB_DRIVER
    5 FUNCTION     SAPLERFC                            LERFCU01                               59
    ARFC_EXECUTE
    4 FUNCTION     SAPLERFC                            LERFCU02                              229
    ARFC_DEST_SHIP
    3 FORM         SAPLERFC                            LERFCV02                               28
    ARFC_DEST_SHIP
    2 FORM         SAPMSSY1                            SAPMSSY1                               69
    REMOTE_FUNCTION_CALL
    1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
    %_RFC_START
    Chosen variables
    Name
    Val.
    No.      13 Ty.          FORM
    Name  F09_IDOC_INSERT_WITH_NUMBER
    CONTROL-MESTYP
    USERCLONE
    554544444222222222222222222222
    53523CFE5000000000000000000000
    C_MESTYP
    FIDCCH
    444444222222222222222222222222
    694338000000000000000000000000
    SY-XFORM
    IDOC_INBOUND_ASYNCHRONOUS
    444454444544545544454445522222
    94F3F9E2F5E4F139E382FEF5300000
    LIST_STATUS-STAPA2
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    C_FUNC
    IDOC_TRANSFORM
    444455544544542222222222222222
    94F3F421E36F2D0000000000000000
    SYST-REPID
    SAPLEDI1
    5454444322222222222222222222222222222222
    310C549100000000000000000000000000000000
    SY-UNAME
    Q63CLNT140
    533444533322
    1633CE414000
    %_DUMMY$$
    2222
    0000
    SY-MSGV1
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SYST-SUBRC
    0
    0000
    0000
    ALE_IDOC_TO_APL_OK
    62
    33
    62
    LIST_CONTAINER_CREATE[]
    Table IT_20[9x1068]
    FUNCTION-POOL=EDI1DATA=LIST_CONTAINER_CREATE[]
    Table reference: 14
    TABH+  0(20) = 070000008036F5B8000000000000000000000000
    TABH+ 20(20) = 0000000E00000014000000090000042CFFFFFFFF
    TABH+ 40(16) = 0400002300000CA0000824C401000000
    store        = 0x070000008036F5B8
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 14    (0x0000000E)
    label        = 20    (0x00000014)
    fill         = 9     (0x00000009)
    leng         = 1068  (0x0000042C)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000048
    occu         = 8     (0x00000008)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x070000008036F610
    pghook       = 0x07000000802D86D0
    idxPtr       = 0x0000000000000000
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    store_id     = 23    (0x00000017)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    LIST_CONTAINER_CREATE
    1400000000000511747000000009E1BPADRML                     00000002#èXD63        070TST_QA140_1
    3333333333333333333333333333434544544222222222222222222222333333330E54332222222233355555433353
    14000000000005117470000000095120142DC0000000000000000000000000000238846300000000070434F11140F1
    CONTROL
    1400000000000511747640 64        2SAPQ63    LSQ63CLNT140
    3333333333333333333333233222222223545533222245533444533322222222222222222222222222222222222222
    14000000000005117476400640000000023101630000C31633CE414000000000000000000000000000000000000000
    G_MAXSYNERR
    1
    0000
    0001
    <%_TABLE_EDID4>
    ALE_DISPATCH_ERROR
    27
    33
    27
    ALE_IDOC_READY_FOR_APL
    64
    33
    64
    %_SPACE
    2
    0
    IDENT
    0000000000000001
    3333333333333333
    0000000000000001
    ALE_IDOC_TO_APL_ERROR
    63
    33
    63
    No.      12 Ty.          FUNCTION
    Name  EDI_DOCUMENT_CLOSE_CREATE_TAB
    IDENTIFIER
    0000000000000001
    3333333333333333
    0000000000000001
    NO_DEQUEUE
    X
    5
    8
    SYN_ACTIVE
    Y
    5
    9
    IDOC_CONTROL
    1400000000000511747640 64        2SAPQ63    LSQ63CLNT140
    3333333333333333333333233222222223545533222245533444533322222222222222222222222222222222222222
    14000000000005117476400640000000023101630000C31633CE414000000000000000000000000000000000000000
    SYNTAX_RETURN
    0
    0000
    0000
    INT_EDIDD[]
    Table IT_10[9x1062]
    FUNCTION-POOL=EDINDATA=G_T_DATA_RECORDS[]
    Table reference: 9
    TABH+  0(20) = 0700000080284B80070000008028530800000000
    TABH+ 20(20) = 000000090000000A0000000900000426FFFFFFFF
    TABH+ 40(16) = 0400000900000AA8000824C401000000
    store        = 0x0700000080284B80
    ext1         = 0x0700000080285308
    shmId        = 0     (0x00000000)
    id           = 9     (0x00000009)
    label        = 10    (0x0000000A)
    fill         = 9     (0x00000009)
    leng         = 1062  (0x00000426)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000039
    occu         = 8     (0x00000008)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x0700000080320D90
    pghook       = 0x07000000802E1508
    idxPtr       = 0x0000000000000000
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    store_id     = 17    (0x00000011)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    hsdir        = 0x0000000000000000
    ext2         = 0x07000000802852A8
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x0700000080284B30
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    NO_IGNORE
    2
    0
    EDI_IDOC_SYNTAX_ERROR_IN
    60
    33
    60
    DOCNUM
    0000000000511747
    3333333333333333
    0000000000511747
    EXCLUSIVE
    E
    4
    5
    SYNCHRONOUS
    S
    5
    3
    APL_TESTIDOC_CHECK_OK
    55
    33
    55
    FREE_RETURN
    0
    0000
    0000
    INT_EDIDD
    1400000000000000001000009E1BPADRML                  00000000##XD63        070TST_QA140_17  X00
    3333333333333333333333333434544544222222222222222222333333330054332222222233355555433353322533
    14000000000000000010000095120142DC0000000000000000000000000000846300000000070434F11140F1700800
    SUB_INT_ACK_POSITIVE
    14
    33
    14
    G_INSERT_OK
    2
    0
    LIST_CONTAINER_INSERT_TMP[]
    Table[initial]
    LIST_CONTAINER_INSERT_TMP
    0000000000000000000000000                              00000000##
    2223333333333333333333333333222222222222222222222222222222333333330022222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    No.      11 Ty.          FUNCTION
    Name  IDOC_INBOUND_WRITE_TO_DB
    PI_DO_HANDLE_ERROR
    X
    5
    8
    PI_NO_DEQUEUE
    X
    5
    8
    PI_RETURN_DATA_FLAG
    X
    5
    8
    PI_RFC_MULTI_CP
    0000
    3333
    0000
    PI_STATUS_MESSAGE
    000000000000000000000000000000000000000000000000000000000000
    2223333333333333333333333333333333333333333333333333333333333332222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    PE_IDOC_NUMBER
    0000000000000001
    3333333333333333
    0000000000000001
    PE_INBOUND_PROCESS_DATA
    140BAPI                                                  6
    3334454222222222222222222222222222222222222222222222222223222222222222222222222222222222222222
    1402109000000000000000000000000000000000000000000000000006000000000000000000000000000000000000
    PE_STATE_OF_PROCESSING
    0
    0000
    0000
    T_DATA_RECORDS[]
    Table IT_10[9x1062]
    T_LINKED_OBJECTS[]
    Table IT_11[0x100]
    FUNCTION-POOL=EDINFORM=ONE_IDOC_STOREDATA=LT_LINKED_OBJECTS[]
    Table reference: 10
    TABH+  0(20) = 000000000000000007000000802853F000000000
    TABH+ 20(20) = 0000000A0000000B0000000000000064FFFFFFFF
    TABH+ 40(16) = 0400000900002BB00010249401000000
    store        = 0x0000000000000000
    ext1         = 0x07000000802853F0
    shmId        = 0     (0x00000000)
    id           = 10    (0x0000000A)
    label        = 11    (0x0000000B)
    fill         = 0     (0x00000000)
    leng         = 100   (0x00000064)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000190
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    store_id     = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    hsdir        = 0x0000000000000000
    ext2         = 0x0700000080285390
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x0700000080285340
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    PC_CONTROL_RECORD
    1400000000000000000    30        2          LSQ63CLNT140
    3333333333333333333222233222222223222222222245533444533322222222222222222222222222222222222222
    14000000000000000000000300000000020000000000C31633CE414000000000000000000000000000000000000000
    %_VIASELSCR
    0
    4
    %_SPACE
    2
    0
    L_STATUS
    64
    33
    64
    L_ALE_SUCCESS_MESSAGE
    B1                  S005                                                  No filters
    4322222222222222222253332222222222222222222222222222222222222222222222222246266676772222222222
    21000000000000000000300500000000000000000000000000000000000000000000000000EF069C45230000000000
    ST_PREVIOUS_PARTNER_DATA-SYNCHK
    X
    5
    8
    C_TRUE
    X
    5
    8
    SYST-REPID
    SAPLEDIR
    5454444522222222222222222222222222222222
    310C549200000000000000000000000000000000
    C_ELEMENT_UNPROCESSED_IDOCS
    Unprocessed_IDocs
    56776667766544667222222222222222
    5E02F353354F94F33000000000000000
    ST_PREVIOUS_STATE_OF_PROCE
    0
    0000
    0000
    ST_INBOUND_PROCESS_DATA-EDIVR2
    6
    3
    6
    SY-MSGV4
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    L_SYN_ACTIVE
    Y
    5
    9
    SY-XFORM
    IDOC_INBOUND_ASYNCHRONOUS
    444454444544545544454445522222
    94F3F9E2F5E4F139E382FEF5300000
    L_SYNTAX_RETURN
    0
    0000
    0000
    %_DUMMY$$
    2222
    0000
    SY-REPID
    SAPLEDIR
    5454444522222222222222222222222222222222
    310C549200000000000000000000000000000000
    No.      10 Ty.          FORM
    Name  ONE_IDOC_STORE
    IDOC_NUMBER_IN
    0000000000000000
    3333333333333333
    0000000000000000
    STATE_OF_PROCESSING_IN
    0
    0000
    0000
    INBOUND_PROCESS_DATA_IN
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    GT_NEW_IDOC_IDENTIFICATIONS[]
    Table[initial]
    G_LAST_IDOC_NUMBER
    0000000000000000
    3333333333333333
    0000000000000000
    SYST-REPID
    SAPLEDIN
    5454444422222222222222222222222222222222
    310C549E00000000000000000000000000000000
    CURRENT_CONTROL_RECORD_IN-DOCNUM
    0000000000000000
    3333333333333333
    0000000000000000
    CONV_ERROR
    2
    0
    C_TRUE
    X
    5
    8
    SY
    0000000000000000000000000000000000000000000000000000000000000000000000000000000200000000000000
    0002000000010009000000000000000000000000000100000001000000010000000000000000004C00000000000000
    STATUS_MESSAGE_IN
    000000000000000000000000000000000000000000000000000000000000
    2223333333333333333333333333333333333333333333333333333333333332222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    C_IDOC_SELECT_AND_WRITE_TO_DB
    5
    3
    5
    SY-REPID
    SAPLEDIN
    5454444422222222222222222222222222222222
    310C549E00000000000000000000000000000000
    STATUS_MESSAGE_IN-STAMID
    22222222222222222222
    00000000000000000000
    GT_NEW_IDOC_IDENTIFICATIONS
    0000000000000000
    3333333333333333222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SPACE
    2
    0
    STATUS_MESSAGE_IN-STAMNO
    000
    333
    000
    RET_FLAG
    X
    5
    8
    G_RFC_CODEPAGE
    0000
    3333
    0000
    RSJOBINFO-JOBSUBRC
    0
    0000
    0000
    SY-XFORM
    IDOC_INBOUND_ASYNCHRONOUS
    444454444544545544454445522222
    94F3F9E2F5E4F139E382FEF5300000
    SY-LANGU
    E
    4
    5
    G_T_DATA_RECORDS[]
    Table IT_10[9x1062]
    LT_LINKED_OBJECTS[]
    Table IT_11[0x100]
    CURRENT_CONTROL_RECORD_IN
    1400000000000000000    30        2          LSQ63CLNT140
    3333333333333333333222233222222223222222222245533444533322222222222222222222222222222222222222
    14000000000000000000000300000000020000000000C31633CE414000000000000000000000000000000000000000
    %_DUMMY$$
    2222
    0000
    SWO_%OBJID
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    No.       9 Ty.          FUNCTION
    Name  IDOC_INBOUND_ASYNCHRONOUS
    IDOC_CONTROL_REC_40[]
    Table IT_3[1x524]
    FUNCTION-POOL=EDINFORM=IDOC_INBOUND_ASYNCHRONOUSDATA=IDOC_CONTROL_REC_40[]
    Table reference: 3
    TABH+  0(20) = 07000000802D876007000000802D449000000000
    TABH+ 20(20) = 0000000300000003000000010000020C000000E0
    TABH+ 40(16) = 0400000900001FE0000A249001000000
    store        = 0x07000000802D8760
    ext1         = 0x07000000802D4490
    shmId        = 0     (0x00000000)
    id           = 3     (0x00000003)
    label        = 3     (0x00000003)
    fill         = 1     (0x00000001)
    leng         = 524   (0x0000020C)
    loop         = 224   (0x000000E0)
    xtyp         = TYPE#000136
    occu         = 10    (0x0000000A)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 0
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x07000000802DB9D8
    pghook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 10    (0x0000000A)
    lineAlloc    = 10    (0x0000000A)
    store_id     = 9     (0x00000009)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    hsdir        = 0x0000000000000000
    ext2         = 0x07000000802D88A0
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x07000000802D8710
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    IDOC_DATA_REC_40[]
    Table IT_4[9x1063]
    FUNCTION-POOL=EDINFORM=IDOC_INBOUND_ASYNCHRONOUSDATA=IDOC_DATA_REC_40[]
    Table reference: 4
    TABH+  0(20) = 07000000802D880807000000802D896000000000
    TABH+ 20(20) = 00000004000000040000000900000427FFFFFFFF
    TABH+ 40(16) = 04000009000020500008249001000000
    store        = 0x07000000802D8808
    ext1         = 0x07000000802D8960
    shmId        = 0     (0x00000000)
    id           = 4     (0x00000004)
    label        = 4     (0x00000004)
    fill         = 9     (0x00000009)
    leng         = 1063  (0x00000427)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000138
    occu         = 8     (0x00000008)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 0
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x07000000802E1550
    pghook       = 0x07000000802D8860
    idxPtr       = 0x0000000000000000
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    store_id     = 12    (0x0000000C)
    shmIsReadOnly = 0     (0x

    Hi Rohan,
    Welcome to SDN!
    This error means that you're trying to duplicate a record on the DB... check the IDOC  number ranges... it might help
    Regards
    Juan
    Please reward with points if helpful

  • Unable to create RAID on SPARC-Enterprise-T5220

    hi:
    i got the following issue on my SPARC-Enterprise-T5220.
    i have constructed the RAID-1 on 4 disks out of 6.
    i have created RAID-1 on OS Disks using raidctl command on single user mode
    and i have created RADI-1 on other two disks. but i'm unable to create RAID-1 on the rest of the two disks.
    here i s the info i am giving
    # format
    Searching for disks...done
    AVAILABLE DISK SELECTIONS:
    0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
    /pci@0/pci@0/pci@2/scsi@0/sd@0,0
    1. c1t1d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
    /pci@0/pci@0/pci@2/scsi@0/sd@1,0
    2. c1t2d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 273>
    /pci@0/pci@0/pci@2/scsi@0/sd@2,0
    3. c1t4d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 136>
    /pci@0/pci@0/pci@2/scsi@0/sd@4,0
    disks 2 and 3 are under raid but where as 0 and 1 are not
    i am trying to construct raid on that disks it is giving following error
    # raidctl -c c1t0d0 c1t1d0
    Creating RAID volume will destroy all data on spare space of member disks, proceed (yes/no)? yes
    Too many arrays.
    here is my OS release information
    Solaris 10 5/08 s10s_u5wos_10 SPARC
    Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.
    Use is subject to license terms.
    Assembled 24 March 2008
    SunOS 5.10 Generic_127127-11 sun4v sparc SUNW,SPARC-Enterprise-T5220
    would any body help me on this.
    thanks in advance
    SN

    Hello sir,
    I work for one of Sun's Channel Development Partners and had a partner site the same problem today, but with a T5240.
    If you check with the "Disk Volumes" section of the T5120/T5220 Admin Guide, it tells us that the integrated LSI controller only supports up to two volumes at a time.
    http://docs.sun.com/source/820-2179-10/Volume-man.html#50606103_28600
    If you need more options for hardware RAID configuration of the internal disks, Sun offers an internal PCI-E SAS RAID HBA:
    SGXPCIESAS-R-INT-Z     
    Sun StorageTek (TM) 8-port internal SAS RAID Host Bus Adapter with RAID 0, 1, 1E, 10, 5, 5EE, 50, 6, 60 support, 256MB of onboard memory and 72 hour Battery Backed Write Cache. RoHS 6. X-Option.
    List Price: $599
    You'd also want this cable kit to go with it:
    SEDX9SA2Z     
    Internal SAS Cable Kit required to use Sun RAID Card SG(X)PCIESAS-R-INT-Z for use with the SPARC Enterprise T5220
    List Price: $40
    Here is documentation about the adapter:
    http://docs.sun.com/app/docs/coll/sas-raid-hba-int

  • Unable to create temporary backing file

    My program is throwing out the error:
    temporary open: /var/tmp/BDB20825: Too many open files
    unable to create temporary backing file
    This happens after my program has been running for about 4 hours. The program appears to run out of file descriptors. The listing of /proc/<PID>/fd shows hundreds of lines naming the same file (/var/tmp/BDB20825), like this:
    lrwx------ 1 zobell users 64 Jul 28 14:41 622 -> /var/tmp/BDB20825 (deleted)
    That file does not exist. I suspect that someone is deleting but failing to close the file. A few open file descriptors with this deleted file occur slowly in the early hours, but not at a fast enough rate to bring the program down when it does. It looks like there is a sudden flood at the end.
    The program repeats this error slowly, and is stuck inside the db code. Here is the gdb backtrace I am seeing every time I interrupt:
    (gdb) where
    #0 0x00e74410 in __kernel_vsyscall ()
    #1 0x003d51dd in ___newselect_nocancel () from /lib/libc.so.6
    #2 0x002e5d39 in __os_sleep () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
    #3 0x002e43f1 in __os_openhandle () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
    #4 0x002e52ad in __os_open () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
    #5 0x002c0357 in __db_tmp_open () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
    #6 0x002c006c in __db_appname () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
    #7 0x002d50c9 in __memp_bhwrite () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
    #8 0x002d4a27 in __memp_alloc () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
    #9 0x002d62ec in __memp_fget () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
    #10 0x00232003 in __bam_new_file () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
    #11 0x002abc79 in __db_new_file () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
    #12 0x002abaff in __db_open () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
    #13 0x002a5d15 in __db_open_pp () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
    #14 0x0080644c in Db::open () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb_cxx-4.6.so
    #15 0x0053ebbe in DbXml::DbWrapper::open (this=0x405bbee0, txn=0x0, type=DB_BTREE, flags=65537, mode=0) at Transaction.hpp:62
    #16 0x00549247 in CacheDatabase (this=0x405bbed8, env=0x9c5a848, type=DB_BTREE, compare=0) at CacheDatabase.cpp:28
    #17 0x005497e2 in DocDatabase (this=0x405bbed8, env=0x9c5a848, compare=0) at CacheDatabase.cpp:46
    #18 0x00584ced in DbXml::Manager::createDocDatabase (this=0x9c5a830, compare=0) at Manager.cpp:694
    #19 0x00519467 in DbXml::CacheDatabaseMinderImpl::verify (this=0xfffffdfe, entry=@0x6ac2f790, cid=-514) at CacheDatabaseMinder.hpp:31
    #20 0x00519398 in DbXml::CacheDatabaseMinderImpl::findOrAllocate (this=0x6ac5b4f0, cid=1, allocate=true) at CacheDatabaseMinder.cpp:71
    #21 0x00518e59 in DbXml::CacheDatabaseMinder::findOrAllocate (this=0x6acd9fa0, mgr=@0x9c5a830, cid=1, allocate=true) at CacheDatabaseMinder.cpp:21
    #22 0x0055b12d in LazyDIResults (this=0x6acd9f98, context=0x6acd9fa0, contextItem=0x4979abc0, expr=@0x9ce5de8, txn=0x0, flags=0) at /devel/tfm/developers/szobell/berkeley-db-xml/dbxml-2.4.16/dbxml/include/dbxml/XmlManager.hpp:80
    #23 0x0052f9cd in DbXml::QueryExpression::execute (this=0x9ce5de8, txn=0x0, contextItem=0x4979abc0, context=@0xbfcb0e04, flags=0) at /devel/tfm/developers/szobell/berkeley-db-xml/dbxml-2.4.16/dbxml/include/dbxml/XmlQueryContext.hpp:86
    #24 0x00565a3a in DbXml::XmlQueryExpression::execute (this=0x0, contextItem=@0xfffffdfe, context=@0xbfcb0e04, flags=4294966782) at /devel/tfm/developers/szobell/berkeley-db-xml/dbxml-2.4.16/dbxml/include/dbxml/XmlValue.hpp:186
    #25 0x0805af4b in XmlRecordWithCounts::ExtractQueryString (this=0xbfcb0dd0, select=@0xbfcb0e2c, result=@0xbfcac1d0, qDocument=0xbfcb0e14) at src/XmlRecordWithCounts.cpp:401
    #26 0x080585f6 in OdRecord::GetRequiredContent (this=0xbfcb0dd0, name=@0xbfcac1e0, origin=@0xbfcac1d0, dest=@0xbfcac1c0, type=@0xbfcac1b0, dist=@0xbfcac198, totalCount=@0xbfcac194, route=@0xbfcac1a0, qDocument=0x0) at src/OdRecord.cpp:143
    #27 0x0804d9c3 in ProcessOd (fpPrivate=0x8e11098, odDb=@0xbfcb0dd0, fdDb=@0xbfcb0d20) at src/BuildFdDb.cpp:263
    #28 0x0804f4c8 in ProcessOneDest (fpPrivate=0x8e11098, odDb=@0xbfcb0dd0, fdDb=@0xbfcb0d20, dest={static npos = 4294967295, _M_dataplus = {<std::allocator<char>> = {<No data fields>}, Mp = 0x9da758c "LAX"}, static Sempty_rep_storage = {0, 0, 69041, 0}}) at src/BuildFdDb.cpp:464
    #29 0x080501cd in main (argc=6, argv=0xbfcb10c4) at src/BuildFdDb.cpp:589
    At this time, the program is trying to extract fields out of an XmlDocument that is the result of a query. The program uses a pre-calculated XmlQueryExpression to extract a specific field. This may not be the best way to extract a field from a document, given the apparent overhead of needing a temporary file!
    My program queries two database files (OD.dbxml and FD.dbxml.new), and uses the information to add records to the second file. The databases are rather big:
    bash-3.2$ ls -l /tmp/*dbxml*
    -rw-rw---- 1 zobell users 5233745920 Jul 28 14:42 /tmp/FD.dbxml.new
    -rw-rw---- 1 zobell users 6539427840 Jul 13 10:16 /tmp/OD.dbxml
    (I keep them in /tmp because everywhere else uses NFS and performance is awful with NFS.)
    My environment:
    Red Hat Enterprise Linux Client release 5.3 (Tikanga) 32 bit.
    Berkeley DB XML 2.4.16, C++ interface.
    Disk space should not be an issue:
    bash-3.2$ df /tmp /var
    Filesystem 1K-blocks Used Available Use% Mounted on
    /dev/mapper/VolGroup00-tmp
    28948572 13044384 14409968 48% /tmp
    /dev/mapper/VolGroup00-root
    144742920 5333544 131938272 4% /
    I ran this program about a year ago and did not see this issue. I have made a few changes and linked to the newer version of the XML database since then. Any help is appreciated.

    I have more information about this problem.
    If I "disable" the routine __os_zerofill() in os_fzero.c, by having it always return (0), I no longer get an exception and my application appears to run smoothly. However, I have not determined what in this routine leads to the exception. And, I have no idea what the short and long term consequences of "disabling" this routine will be....
    -Coralie

  • Acrobat 8 Pro now unable to create pdf files

    Been using Acrobat 8 for well over a year.  Installed new release of AutoCAD 2012, now unable to create pdf files from AutoCAD or MS Office programs.  Can anybody help?

    You may still want to at least give a repair a shot. Won't hurt and sometimes customer suport (I assume you mean Adobe customer support?) will miss some things. I believe in your version you can find it under the Help menu.
    BtlMage918 wrote:
    No because the
    customer support person I spoke with first said the problem was within the
    creation portion of the program and did not fell that reinstallation or
    deactivate/activate would resolve.
    Charles Blake
    Annette Miller Architects
    204 S. Ludlow St., Suite 310
    Dayton, Ohio 45402
    937.228.7841
    <http://www.amillerarchitects.com/> www.amillerarchitects.com

  • Unable to create xml from xml schema

    JDeveloper 10.1.3 EA1
    I am unable to create a new xml file from an xml schema when the starting root element is a complex type (but it works with a simple type). It does not matter if the xml schema is registered within JDeveloper.
    Is this a bug or intended behaviour?
    Error message:
    ''XML Document from XML Schema creation could not be competed succesfully. Make sure the source schema is valid and that you have write permissions to the output directory."
    NB The xml schema is valid and I have write permissions on the specified directory.

    When I do not register this (or other) schema with JDeveloper, I can create an xml document from xml schema. However, when I register this schema and then try to generate an xml document (either from the registered xsd either from a filesystem xsd) with person as starting node it fails with the mentioned error. However, when I use city as starting node it is generated successfully.
    <?xml version="1.0" encoding="windows-1252" ?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns="http://www.amis.nl/demo/hrm"
    targetNamespace="http://www.amis.nl/demo/hrm"
    elementFormDefault="qualified">
    <xsd:element name="person">
    <xsd:annotation>
    <xsd:documentation>
    A sample complex element
    </xsd:documentation>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="name" type="xsd:string"/>
    <xsd:element name="length" type="xsd:int"/>
    <xsd:element name="weight" type="xsd:int" />
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="city" type="xsd:string">
    <xsd:annotation>
    <xsd:documentation>
    A sample simple element.
    </xsd:documentation>
    </xsd:annotation>
    </xsd:element>
    </xsd:schema>

  • Unable to create the type with the name 'MSORA'. (Microsoft.SqlServer.ManagedDTS)

    I am attempting to use the Integration Services Import Project Wizard within Microsoft Visual Studio and am getting this error
    Unable to create the type with the name 'MSORA'. (Microsoft.SqlServer.ManagedDTS)
    upon Import.
    Can anyone shed some light for me on this cryptique error message?
    Thanks for your review and am hopeful for a reply.

    If you have the SSIS and SSDT (BIDS) installed then
    I believe the DTS assemblies got derigistered, a typical outcome of corrupted software, so a full re-install would be the best option. VS +SQL Server  + more
    Otherwise, as a quick fix try to
    reference the SSIS assemblies, like Microsoft.SQLServer.ManagedDTS.dll + more.
    They are by default in C:\Program Files\Microsoft SQL Server\<number>\SDK\Assemblies.
    Arthur
    MyBlog
    Twitter

  • Unable to create the type with the name 'ODATA'

    On a test server with VS 2012 and SQL 2012 installed, I have created an SSIS project in project deployment mode. In the packages of the project I use the Odata source for SSIS. The packages run fine in VS 2012. But when I deploy the package to the Integration
    Services catalog on the same server as where I am running VS 2012 I get a deployment error:
    ‘Failed to deploy project. For more information, query the operation_messages view for the operation identifier '25084'.  (Microsoft SQL Server, Error: 27203)'
    When I read this message from the SSISDB database, I see the problem with ODATA.
    use SSISDB
    go
    select * from catalog.operation_messages where operation_id = 25084
    --Failed to deploy the project. Fix the problems and try again later.:Unable to create the type with the name 'ODATA'.
    As I said: the packages with the Odata run without error when tested from within VS2012 on the SAME server. When I deploy the project from Visual Studio I get the error. 
    For completeness: I have also tried deployment from VS2012 to another server where the SSIS Odata source has bene deployed. Also to no avail.
    Jan D'Hondt - SQL server BI development

    The next possiblity for me was to convert the project to Package deployment and see what the result I get. I have converted my project with package connections from project deployment to Package deployment. Then I deployed the package on the server in MSDB
    catalog from SSIS. I.e. I connect with SSMS to Integration Services as an administrator and under the MSDB folder I added a new folder for my package. I then imported the dtsx into the mdsb package store. The Import worked. Still from within SSMS and connected
    to the Integration Services, i right-clicked on the package in the MSDB store and selected 'Run package'. In the Execute Package dialog window, I clicked on 'Execute' and the package actually ran. The Odata connector was opened, it read the data and imported
    into my database.
    This experience made me realize what the real culprit  was: The OData connector is a 32-bit connector in SQL Server 2012. 
    To prove this: with SSMS I connected to the SQL database server and in the Integration services catalog, i right-clicked on the package that was deployed in Project deployment mode, then selected 'Execute...'. In the execute dialog windo in the 'Advanced'
    tab I checked 32-bit runtime. And the package ran.
    To wrap it all up:
    The Project deployment will work, but not with the Odata source as project connection. The Odata connection must be defined in each package as a package connection.
    Run the deployed packages in 32-bit mode on the server
    Jan D'Hondt - SQL server BI development

  • Unable to create the test suits file!

    Dear Experts!
    Getting the "Unable to create the test suits file!" error while opening .bpel file in JDeveloper 10.1.3.5. Also, all the partner links showing warning symbol. When I click on them, getting the following error:
    ERROR:WSDLException: faultCode=INVALID_WSDL: Invalid XML in document at: Start of root element expected.
    Looks like partner links are not mapped correctly. Could you please throw some light, where I need to fix the issue.
    Appreciate your help.
    Thank you.

    I had similar issue sometimes back, error was because sample xml my test was using wasn't conforming to my code. In my case, I didn't write test suite so deployment was successful and was getting error while testing post deployment. In your case, test suite will execute.
    Try to follow your xslt mapping or any xpath statements within bpel flow, it must be having direct mapping of some element from source but your sample input xml might not be having that element and hence resulting in error. Try iterative debugging by adding more elements in input xml.
    Regards,
    Ankit

  • Unable to create a whole root zone

    Hi Folks,
    I wanted to create a whole-root zone. I am unable to create one :(. Did some one encounter this problem ?.
    BTW: I have SC 3.2 installed on this two node cluster. I was able to validate our Data services on this setup without any problem Now I am trying to experiment with zones, by creating zones. I am unable to move further with my validation of our data services on zones.
    *) mkdir -m 700 /export/zone-1
    *) The version of the OS used
    # cat /etc/release
    Solaris 10 11/06 s10s_u3wos_09 SPARC
    Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
    Use is subject to license terms.
    Assembled 01 November 2006
    # zonecfg -z zone-1
    zone-1: No such zone configured
    Use 'create' to begin configuring a new zone.
    zonecfg:zone-1> create
    zonecfg:zone-1> remove inherit-pkg-dir dir=/sbin
    zonecfg:zone-1> remove inherit-pkg-dir dir=/usr
    zonecfg:zone-1> remove inherit-pkg-dir dir=/platform
    zonecfg:zone-1> remove inherit-pkg-dir dir=/lib
    zonecfg:zone-1> set autoboot=true
    zonecfg:zone-1> set zonepath=/export/zone-1
    zonecfg:zone-1> add net
    zonecfg:zone-1:net> set address=192.18.75.237
    zonecfg:zone-1:net> set physical=eri0
    zonecfg:zone-1:net> end
    zonecfg:zone-1> info
    zonename: zone-1
    zonepath: /export/zone-1
    autoboot: true
    pool:
    limitpriv:
    net:
    address: 192.18.75.237
    physical: eri0
    zonecfg:zone-1> verify
    zonecfg:zone-1> commit
    zonecfg:zone-1> exit
    # cat /etc/zones/zone-1.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE zone PUBLIC "-//Sun Microsystems Inc//DTD Zones//EN" "file:///usr/share/lib/xml/dtd/zonecfg.dtd.1">
    <!--
    DO NOT EDIT THIS FILE. Use zonecfg(1M) instead.
    -->
    <zone name="zone-1" zonepath="/export/zone-1" autoboot="true">
    <network address="192.18.75.237" physical="eri0"/>
    </zone>
    # zoneadm list -civ
    ID NAME STATUS PATH
    0 global running /
    - zone-1 configured /export/zone-1
    # zoneadm -z zone-1 verify
    # zoneadm -z zone-1 install
    Preparing to install zone <zone-1>.
    Creating list of files to copy from the global zone.
    Copying <6080> files to the zone.
    Initializing zone product registry.
    Determining zone package initialization order.
    Preparing to initialize <1071> packages on the zone.
    Initialized <1071> packages on zone.
    Zone <zone-1> is initialized.
    Installation of these packages generated errors: <SUNWsczr SUNWdtlog SUNWsmmgr>
    Installation of <1> packages was skipped.
    Installation of these packages generated warnings: <SUNWcsr SUNWxwplr SUNWfontconfig-root SUNWpcr SUNWdtdmr SUNWtnamr SUNWkrbr SUNWtnetr SUNWdoc SUNWppror SUNWocfr SUNWvolr SUNWnfscr SUNWwbcor SUNWwebminr SUNWgssc SUNWnisr SUNWypr SUNWipplr SUNWaccr SUNWbsr SUNWdhcsr SUNWatfsr SUNWkdcr SUNWapch2r SUNWbindr SUNWbnur SUNWcnsr SUNWpsr SUNWsacom SUNWnfssr SUNWntpr SUNWftpr SUNWrcapr SUNWrcmdr SUNWslpr SUNWsndmr SUNWsshdr SUNWstsfr SUNWswupclr>
    The file </export/zone-1/root/var/sadm/system/logs/install_log> contains a log of the zone installation.
    # pkginfo -i SUNWsczr
    application SUNWsczr Sun Cluster (non-global zones support)
    # pkginfo -i SUNWsczr
    application SUNWsczr Sun Cluster (non-global zones support)
    # pkginfo -i SUNWdtlog
    system SUNWdtlog System boot for Desktop Login
    # pkginfo -i SUNWsmmgr
    system SUNWsmmgr System Management Agent Startup scripts
    *** package <SUNWsczr> failed to install with fatal errors:
    WARNING: attribute verification of </export/zone-1/root/etc/init.d/stoprgm> failed
    pathname does not exist
    NOTE: When the package <SUNWsczr> was installed in the global zone, the file <etc/init.d/stoprgm> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone <zone-1> in the file </export/zone-1/root/etc/init.d/stoprgm>.
    ERROR : i.manifest cannot find archived files in /var/sadm/pkg/SUNWsczr/save/pspool/SUNWsczr/archive.
    pkgadd: ERROR: class action script did not complete successfully
    Installation of <SUNWsczr> on zone <zone-1> failed.
    *** package <SUNWnisr> installed with warnings:
    WARNING: attribute verification of </export/zone-1/root/etc/nsswitch.nis> failed
    pathname does not exist
    NOTE: When the package <SUNWnisr> was installed in the global zone,
    the file <etc/nsswitch.nis> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/etc/nsswitch.nis>.
    WARNING: attribute verification of </export/zone-1/root/etc/nsswitch.nisplus> failed
    pathname does not exist
    NOTE: When the package <SUNWnisr> was installed in the global zone,
    the file <etc/nsswitch.nisplus> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/etc/nsswitch.nisplus>.
    WARNING: attribute verification of </export/zone-1/root/lib/svc/method/nisplus> failed
    pathname does not exist
    NOTE: When the package <SUNWnisr> was installed in the global zone,
    the file <lib/svc/method/nisplus> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/lib/svc/method/nisplus>.
    WARNING: attribute verification of </export/zone-1/root/var/nis/NIS+LDAPmapping.template> failed
    pathname does not exist
    NOTE: When the package <SUNWnisr> was installed in the global zone,
    the file <var/nis/NIS+LDAPmapping.template> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/var/nis/NIS+LDAPmapping.template>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWnisr/save/pspool/SUNWnisr/reloc/var/svc/manifest/network/ nis/client.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWnisr/save/pspool/SUNWnisr/reloc/var/svc/manifest/network/ rpc/nisplus.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWnisr/save/pspool/SUNWnisr/reloc/var/svc/manifest/network/ rpc/rex.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/client.xml> failed
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/client.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/nisplus.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/rex.xml> failed
    pathname does not exist
    Installation of <SUNWnisr> on zone <zone-1> partially
    failed.
    *** package <SUNWypr> installed with warnings:
    WARNING: attribute verification of </export/zone-1/root/var/yp/updaters> failed
    pathname does not exist
    NOTE: When the package <SUNWypr> was installed in the global zone,
    the file <var/yp/updaters> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/var/yp/updaters>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWypr/save/pspool/SUNWypr/reloc/var/svc/manifest/network/ni s/passwd.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWypr/save/pspool/SUNWypr/reloc/var/svc/manifest/network/ni s/server.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWypr/save/pspool/SUNWypr/reloc/var/svc/manifest/network/ni s/update.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWypr/save/pspool/SUNWypr/reloc/var/svc/manifest/network/ni s/xfr.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/passwd.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/server.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/update.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nis/xfr.xml> failed
    pathname does not exist
    Installation of <SUNWypr> on zone <zone-1> partially
    failed.
    *** package <SUNWipplr> installed with warnings:
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWipplr/save/pspool/SUNWipplr/reloc/var/svc/manifest/applic ation/print/ipp-listener.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/application/print/ipp-listener.xml> failed
    pathname does not exist
    Installation of <SUNWipplr> on zone <zone-1> partially
    failed.
    *** package <SUNWaccr> installed with warnings:
    WARNING: attribute verification of </export/zone-1/root/lib/svc/method/svc-sar> failed
    pathname does not exist
    NOTE: When the package <SUNWaccr> was installed in the global zone,
    the file <lib/svc/method/svc-sar> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/lib/svc/method/svc-sar>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWaccr/save/pspool/SUNWaccr/reloc/var/svc/manifest/system/s ar.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/system/sar.xml> failed
    pathname does not exist
    Installation of <SUNWaccr> on zone <zone-1> partially
    failed.
    *** package <SUNWbsr> installed with warnings:
    WARNING: attribute verification of </export/zone-1/root/etc/rpld.conf> failed
    pathname does not exist
    NOTE: When the package <SUNWbsr> was installed in the global zone,
    the file <etc/rpld.conf> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/etc/rpld.conf>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWbsr/save/pspool/SUNWbsr/reloc/var/svc/manifest/network/ra rp.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWbsr/save/pspool/SUNWbsr/reloc/var/svc/manifest/network/rp c/bootparams.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rarp.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/bootparams.xml> failed
    pathname does not exist
    Installation of <SUNWbsr> on zone <zone-1> partially
    failed.
    *** package <SUNWdhcsr> installed with warnings:
    WARNING: attribute verification of </export/zone-1/root/etc/init.d/dhcp> failed
    pathname does not exist
    NOTE: When the package <SUNWdhcsr> was installed in the global zone,
    the file <etc/init.d/dhcp> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/etc/init.d/dhcp>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWdhcsr/save/pspool/SUNWdhcsr/reloc/var/svc/manifest/networ k/dhcp-server.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/dhcp-server.xml> failed
    pathname does not exist
    Installation of <SUNWdhcsr> on zone <zone-1> partially
    failed.
    *** package <SUNWatfsr> installed with warnings:
    WARNING: attribute verification of </export/zone-1/root/lib/svc/method/svc-autofs> failed
    pathname does not exist
    NOTE: When the package <SUNWatfsr> was installed in the global zone,
    the file <lib/svc/method/svc-autofs> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/lib/svc/method/svc-autofs>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWatfsr/save/pspool/SUNWatfsr/reloc/var/svc/manifest/system /filesystem/autofs.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/system/filesystem/autofs.xml> failed
    pathname does not exist
    Installation of <SUNWatfsr> on zone <zone-1> partially
    failed.
    *** package <SUNWkdcr> installed with warnings:
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWkdcr/save/pspool/SUNWkdcr/reloc/var/svc/manifest/network/ security/krb5_prop.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/security/krb5_prop.xml> failed
    pathname does not exist
    Installation of <SUNWkdcr> on zone <zone-1> partially
    failed.
    WARNING: attribute verification of </export/zone-1/root/var/apache2/icons/world2.gif> failed
    pathname does not exist
    NOTE: When the package <SUNWapch2r> was installed in the global zone,
    the file <var/apache2/icons/world2.gif> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/var/apache2/icons/world2.gif>.
    WARNING: attribute verification of </export/zone-1/root/var/apache2/icons/world2.png> failed
    pathname does not exist
    NOTE: When the package <SUNWapch2r> was installed in the global zone,
    the file <var/apache2/icons/world2.png> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/var/apache2/icons/world2.png>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWapch2r/save/pspool/SUNWapch2r/reloc/var/svc/manifest/netw ork/http-apache2.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/http-apache2.xml> failed
    pathname does not exist
    Installation of <SUNWapch2r> on zone <zone-1> partially
    failed.
    *** package <SUNWbindr> installed with warnings:
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWbindr/save/pspool/SUNWbindr/reloc/var/svc/manifest/networ k/dns/server.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/dns/server.xml> failed
    pathname does not exist
    Installation of <SUNWbindr> on zone <zone-1> partially
    failed.
    *** package <SUNWbnur> installed with warnings:
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWbnur/save/pspool/SUNWbnur/reloc/var/svc/manifest/network/ uucp.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/uucp.xml> failed
    pathname does not exist
    Installation of <SUNWbnur> on zone <zone-1> partially
    failed.
    *** package <SUNWcnsr> installed with warnings:
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ chargen.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ daytime.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ discard.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ echo.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWcnsr/save/pspool/SUNWcnsr/reloc/var/svc/manifest/network/ time.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/chargen.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/daytime.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/discard.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/echo.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/time.xml> failed
    pathname does not exist
    Installation of <SUNWcnsr> on zone <zone-1> partially
    failed.
    WARNING: attribute verification of </export/zone-1/root/etc/lp/fd/pr.fd> failed
    pathname does not exist
    NOTE: When the package <SUNWpsr> was installed in the global zone,
    the file <etc/lp/fd/pr.fd> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/etc/lp/fd/pr.fd>.
    WARNING: attribute verification of </export/zone-1/root/lib/svc/method/print-svc> failed
    pathname does not exist
    NOTE: When the package <SUNWpsr> was installed in the global zone,
    the file <lib/svc/method/print-svc> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/lib/svc/method/print-svc>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWpsr/save/pspool/SUNWpsr/reloc/var/svc/manifest/applicatio n/print/server.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/application/print/server.xml> failed
    pathname does not exist
    Installation of <SUNWpsr> on zone <zone-1> partially
    failed.
    WARNING: attribute verification of </export/zone-1/root/var/snmp/mib/sun.mib> failed
    pathname does not exist
    NOTE: When the package <SUNWsacom> was installed in the global zone,
    the file <var/snmp/mib/sun.mib> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/var/snmp/mib/sun.mib>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWsacom/save/pspool/SUNWsacom/reloc/etc/init.d/init.dmi> is corrupt
    file size <373> expected <1125> actual
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWsacom/save/pspool/SUNWsacom/reloc/etc/init.d/init.snmpdx& gt; is corrupt
    file size <382> expected <685> actual
    ERROR: attribute verification of </export/zone-1/root/etc/init.d/init.dmi> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/etc/init.d/init.snmpdx> failed
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWsacom/save/pspool/SUNWsacom/reloc/var/svc/manifest/applic ation/management/dmi.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWsacom/save/pspool/SUNWsacom/reloc/var/svc/manifest/applic ation/management/snmpdx.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/application/management/dmi.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/application/management/snmpdx.xml> failed
    pathname does not exist
    Installation of <SUNWsacom> on zone <zone-1> partially
    failed.
    *** package <SUNWdtlog> failed to install with fatal errors:
    WARNING: attribute verification of </export/zone-1/root/etc/init.d/dtlogin> failed
    pathname does not exist
    NOTE: When the package <SUNWdtlog> was installed in the global zone,
    the file <etc/init.d/dtlogin> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/etc/init.d/dtlogin>.
    WARNING: attribute verification of </export/zone-1/root/lib/svc/method/svc-dtlogin> failed
    pathname does not exist
    NOTE: When the package <SUNWdtlog> was installed in the global zone,
    the file <lib/svc/method/svc-dtlogin> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/lib/svc/method/svc-dtlogin>.
    ERROR : i.manifest cannot find archived files in /var/sadm/pkg/SUNWdtlog/save/pspool/SUNWdtlog/archive.
    pkgadd: ERROR: class action script did not complete successfully
    Installation of <SUNWdtlog> on zone <zone-1> failed.
    *** package <SUNWnfssr> installed with warnings:
    WARNING: attribute verification of </export/zone-1/root/lib/svc/method/nfs-server> failed
    pathname does not exist
    NOTE: When the package <SUNWnfssr> was installed in the global zone,
    the file <lib/svc/method/nfs-server> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/lib/svc/method/nfs-server>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWnfssr/save/pspool/SUNWnfssr/reloc/var/svc/manifest/networ k/nfs/rquota.xml> is corrupt
    pathname does not exist
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWnfssr/save/pspool/SUNWnfssr/reloc/var/svc/manifest/networ k/nfs/server.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nfs/rquota.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/nfs/server.xml> failed
    pathname does not exist
    Installation of <SUNWnfssr> on zone <zone-1> partially
    failed.
    *** package <SUNWntpr> installed with warnings:
    WARNING: attribute verification of </export/zone-1/root/etc/inet/ntp.server> failed
    pathname does not exist
    NOTE: When the package <SUNWntpr> was installed in the global zone,
    the file <etc/inet/ntp.server> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/etc/inet/ntp.server>.
    WARNING: attribute verification of </export/zone-1/root/lib/svc/method/xntp> failed
    pathname does not exist
    NOTE: When the package <SUNWntpr> was installed in the global zone,
    the file <lib/svc/method/xntp> was also installed. After the file was
    installed in the global zone, the contents and/or attributes of the file
    changed. The contents of this file must never be changed. As a result,
    the changes in this file have been duplicated in the non-global zone
    <zone-1> in the file </export/zone-1/root/lib/svc/method/xntp>.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWntpr/save/pspool/SUNWntpr/reloc/var/svc/manifest/network/ ntp.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/ntp.xml> failed
    pathname does not exist
    Installation of <SUNWntpr> on zone <zone-1> partially
    failed.
    *** package <SUNWftpr> installed with warnings:
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWftpr/save/pspool/SUNWftpr/reloc/var/svc/manifest/network/ ftp.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/ftp.xml> failed
    pathname does not exist
    Installation of <SUNWftpr> on zone <zone-1> partially
    failed.
    *** package <SUNWrcapr> installed with warnings:
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWrcapr/save/pspool/SUNWrcapr/reloc/var/svc/manifest/system /rcap.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/system/rcap.xml> failed
    pathname does not exist
    Installation of <SUNWrcapr> on zone <zone-1> partially
    failed.
    pkgadd: ERROR: source path </var/sadm/pkg/SUNWrcmdr/save/pspool/SUNWrcmdr/reloc/var/svc/manifest/networ k/talk.xml> is corrupt
    pathname does not exist
    chmod: WARNING: can't access /export/zone-1/root/etc/svc/repository.db
    chown: /export/zone-1/root/etc/svc/repository.db: No such file or directory
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/comsat.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/finger.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/login.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rexec.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/rstat.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/rusers.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/spray.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/rpc/wall.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/shell.xml> failed
    pathname does not exist
    ERROR: attribute verification of </export/zone-1/root/var/svc/manifest/network/talk.xml> failed
    pathname does not exist
    Installation of <SUNWrcmdr> on zone <zone-1> partially
    failed.
    WARNING: attribute verification of </export/zone-1/root/etc/sma/snmp/snmpconf-data/snmptrapd-data/traphandle> ; failed
    pathname does not exist
    NOTE: When the package <SUNWsmmgr> was installed in the global zone,
    the file <etc/sma/snmp/snmpconf-data/snmptrapd-data/traphandle> was also installed. Af

    Hello,
    I still get the errors.
    # zonecfg -z zone-one
    zone-one: No such zone configured
    Use 'create' to begin configuring a new zone.
    zonecfg:zone-one> create -b
    zonecfg:zone-one> set autoboot=true
    zonecfg:zone-one> set zonepath=/export/zone-one
    zonecfg:zone-one> add net
    zonecfg:zone-one:net> set physical=eri0
    zonecfg:zone-one:net> set address=192.18.xx.xxx
    zonecfg:zone-one:net> end
    zonecfg:zone-one> verify
    zonecfg:zone-one> commit
    zonecfg:zone-one> exit
    # zoneadm -z zone-one verify
    # zoneadm -z zone-one install
    Preparing to install zone <zone-one>.
    Creating list of files to copy from the global zone.
    Copying <6080> files to the zone.
    Initializing zone product registry.
    Determining zone package initialization order.
    Preparing to initialize <1071> packages on the zone.
    Initialized <1071> packages on zone.
    Zone <zone-one> is initialized.
    Installation of these packages generated errors: <SUNWsczr SUNWdtlog SUNWsmmgr>
    Installation of <1> packages was skipped.
    Installation of these packages generated warnings: <SUNWcsr SUNWxwplr SUNWfontconfig-root SUNWpcr SUNWdtdmr SUNWtnamr SUNWkrbr SUNWtnetr SUNWdoc SUNWppror SUNWocfr SUNWvolr SUNWnfscr SUNWwbcor SUNWwebminr SUNWgssc SUNWnisr SUNWypr SUNWipplr SUNWaccr SUNWbsr SUNWdhcsr SUNWatfsr SUNWkdcr SUNWapch2r SUNWbindr SUNWbnur SUNWcnsr SUNWpsr SUNWsacom SUNWnfssr SUNWntpr SUNWftpr SUNWrcapr SUNWrcmdr SUNWslpr SUNWsndmr SUNWsshdr SUNWstsfr SUNWswupclr>
    The file </export/zone-1/root/var/sadm/system/logs/install_log> contains a log of the zone installation.
    _DD                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • Unable to create position hierarchy in organization model

    I was unable to create position hierarchy in organizational hierarchy. I want to maintain position hierarchy within an organization. But SAP CRM is not allowing that. I was able to create organizational hierarchy. Please let me know, how can I maintain the position hierarchy within the same organization?
    --hari

    Hi hari,
    it is only possible to have a hierarchy with two levels on position level. Therefore you create two positions below your organization (tx ppoma_crm). At one of these positions you set the flag "Head of own organizational unit" at the Basic data tab of the position (To see this, you need to display the Details of the positions at the bottom of the screen). Now you can assign a business partner (or more)  to this position which is (are)  the Head of this unit.
    If you need a more complex hierarchy you have to use organizations to show this.
    Hope it helps!
    Kind regards
    Christian

Maybe you are looking for

  • How can I share files between two users? or merge the user accounts

    my laptop came home from the shop with two user accounts -never noticed that before - and some files are in one user account, some in another. I want to share them so I can just use one account. I just upgraded to Lion, so that may be an issue. Best

  • SQL 2012 Reporting Services Print Control... FIX?

    I have an web site that uses ActiveX print control and when there is a SQL update it breaks the print control for all the end users and I have to walk around and enter my admin username/pass to fix this.I have tried a number of fixes such as:Batch sc

  • Text to Speech Crashes

    Text to speech keeps crashing on my brand new Mac Mini running 10.5.1 Console Says: 12/15/07 1:58:05 AM com.apple.launchd[79] ([0x0-0x26026].com.apple.speech.SpeechService[203]) Exited abnormally: Bus error

  • How to restrict grant connect through with Data Vault

    I need to restrict the ability to grant proxy privileges in the database. This is the statement: alter user USER_A grant connect through USER_B; I tried creating this rule that looks at the sql text for %CONNECT THROUGH% in the statement and then add

  • Deploying against a JSP site using JSTL

    I am reviewing Contribute for use at my company. Our current corp site is deployed in JSP and makes extensive use of the Java Standard Tag Library, especially for writing dynamic URLs to content such as images, pdf, and application download. Can Cont