Highlighted
Contributor.. Contributor..
Contributor..
403 views

After installation, the following error during data upload . help me

Starting upload process....
Application and sample data upload to the configured database failed.
Please check if the database is empty and the SQL user has rights to create tables,
check smconfig.log for additional detail.
Invoking shutipc...
Shutipc completed successfully.
License verification passed.

 

smconfig.log

  3376(  5552) 07/22/2016 13:39:13  RTE I Using "utalloc" memory manager, mode [0]
  3376(  5552) 07/22/2016 13:39:13  RTE I Command line: "D:\itsmapp\Service Manager 9.40\Server\RUN\sm" -system_load "-system_directory:D:\itsmapp\Service Manager 9.40\Server\data" "-log:D:\itsmapp\Service Manager 9.40\Server\smconfig.log"
  3376(  5552) 07/22/2016 13:39:13  RTE I Process sm 9.40.0015 () System: 13080 (0x784DFB00) on PC (x64 64-bit) running Windows (6.2 Build 9200) Timezone GMT+09:00 Locale ko_KR from itsmdev
  3376(  5552) 07/22/2016 13:39:13  RTE I Creating resources for system '13080' with key 0x784DFB00
  3376(  5552) 07/22/2016 13:39:13  RTE W The shared memory size 32000000 is less than the recommended size 134217728
  3376(  5552) 07/22/2016 13:39:13  RTE I Created shared memory of size 32000000 using key 0x784DFB00 and attached to it at address 0x80000000
  3376(  5552) 07/22/2016 13:39:13  RTE I JVM successfully created
  3376(  5552) 07/22/2016 13:39:13 JRTE I Java version: 1.7.0_67
  3376(  4252) 07/22/2016 13:39:13 JRTE I Starting Memory Monitoring thread to check for memory every 15 seconds.
  3376(  4252) 07/22/2016 13:39:13  RTE I Using "utalloc" memory manager, mode [0]
  3376(  5552) 07/22/2016 13:39:13  RTE I Host network address: 10.10.119.81
  3376(  5552) 07/22/2016 13:39:13  RTE I Connection to dbtype 'oracle10' Oracle server 'ITSMDEV' as user 'smadmin' successful
  3376(  5552) 07/22/2016 13:39:13  RTE I Connected to Oracle Version 11.2.0.4.0
  3376(  5552) 07/22/2016 13:39:13  RTE I Oracle Client version: 11.2.0.4.0
  3376(  5552) 07/22/2016 13:39:13  RTE I Oracle server settings for language, territory and character set: KOREAN_KOREA.UTF8 (AL16UTF16)
  3376(  5552) 07/22/2016 13:39:13  RTE I OCI Client settings for language, territory and character set: AMERICAN_AMERICA.AL32UTF8 (UTF16)
  3376(  5552) 07/22/2016 13:39:13  RTE W Oracle instance setting for NLS_SORT could not be determined. Default to BINARY
  3376(  5552) 07/22/2016 13:39:13  RTE I Oracle instance setting for NLS_COMP is set to BINARY
  3376(  5552) 07/22/2016 13:39:13  RTE I Oracle session is set up in BINARY mode
  3376(  5552) 07/22/2016 13:39:13  RTE I dbdict file does not exist, system_load will proceed.
  3376(  5552) 07/22/2016 13:39:13  RTE W Unable to open SYSPUBLISH dbdict.  Publish/Subscribe service disabled.
  3376(  5552) 07/22/2016 13:39:13 JRTE I JGroups 3.2.0.Final
  6108(  4660) 07/22/2016 13:39:14  RTE I Using "utalloc" memory manager, mode [0]
  6108(  4660) 07/22/2016 13:39:14  RTE I Command line: "D:\itsmapp\Service Manager 9.40\Server\RUN\sm" -shutipc "-log:D:\itsmapp\Service Manager 9.40\Server\smconfig.log"
  6108(  4660) 07/22/2016 13:39:14  RTE I -Memory : S(52368) O(99612) MAX(156076) - MALLOC's Total(97)
  6108(  4660) 07/22/2016 13:39:14  RTE I Thread termination in progress
  6108(  4660) 07/22/2016 13:39:14  RTE E Unable to obtain SYSTEM lock in interm().
  6108(  4660) 07/22/2016 13:39:14  RTE I Process termination cleanup complete (exit code=0)
  1404(  5020) 07/22/2016 13:39:14  RTE I Using "utalloc" memory manager, mode [0]
  1404(  5020) 07/22/2016 13:39:14  RTE I Command line: "D:\itsmapp\Service Manager 9.40\Server\RUN\sm" -instantOn "-log:D:\itsmapp\Service Manager 9.40\Server\smconfig.log"
  1404(  5020) 07/22/2016 13:39:14  RTE I Process sm 9.40.0015 () System: 13080 (0x784DFB00) on PC (x64 64-bit) running Windows (6.2 Build 9200) Timezone GMT+09:00 Locale ko_KR from itsmdev
  1404(  5020) 07/22/2016 13:39:14  RTE I Creating resources for system '13080' with key 0x784DFB00
  1404(  5020) 07/22/2016 13:39:14  RTE W The shared memory size 32000000 is less than the recommended size 134217728
  1404(  5020) 07/22/2016 13:39:14  RTE I Created shared memory of size 32000000 using key 0x784DFB00 and attached to it at address 0x80000000
  1404(  5020) 07/22/2016 13:39:14  RTE I JVM successfully created
  1404(  5020) 07/22/2016 13:39:14 JRTE I Java version: 1.7.0_67
  1404(  5672) 07/22/2016 13:39:14 JRTE I Starting Memory Monitoring thread to check for memory every 15 seconds.
  1404(  5672) 07/22/2016 13:39:14  RTE I Using "utalloc" memory manager, mode [0]

 

 

Database rights are connect, resource, select any dictionary

 

HELP ME~~~

 

 

0 Likes
1 Reply
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: After installation, the following error during data upload . help me

If your Oracle is installed on a different box from the SM server, you will need to install the 32bit version of Oracle Client for SM Server to communicate with 32bit SM Server. 64bit version of Oracle Client can cause issue like this. It will mention connection is fine but because its 64bit, SM server will fail to work on it.

If your Oracle is on the same box as the SM server, you might want to double check the steps from the interactive install guide. Sometimes people, get the Oracle server name or the db name mixed up. Also make sure the userid smadmin is defaulting to your sm db.

I also noticed this warning, The shared memory size 32000000 is less than the recommended size 134217728. You may want to increase the shared memory size in sm.ini to the recommended to prevent future issues.

From the online install guide:

 

  • Create server connections. Every Service Manager thread, foreground, or background, requires a connection to your RDBMS. Service Manager background processors require 17 connections to run. Make sure that you allocate enough connections for all of your users. For additional information, refer to your RDBMS vendor documentation.
  • Create a login ID and password for Service Manager to use to connect to your Oracle server. When you log on to Service Manager, it creates a table in the default table space defined for that login ID. The login ID must have the following privileges:

    • Connect
    • Create, Alter, Drop a table
    • Create, Alter, Drop an index
    • Select Any Dictionary
    • Alter Session Privileges

    You can provide these privileges to an Oracle user by using the following oracle statements:

    create user <smadmin> identified by <smadmin> default
    tablespace <users> quota unlimited on <users>;
    grant connect, resource, select any dictionary to <smadmin>;

    Note: CREATE/ALTER/DROP TABLE privileges are only required during installation and creation of new Service Manager tables if you allow Service Manager to issue the DDL to create tables and indexes.

  • Service Manager supports case-insensitivity for Oracle 11.2.0.3 and later. For earlier versions of Oracle, Service Manager requires a case-sensitive database. Click the appropriate task below for instructions on setting case-sensitivity.

    ClosedSet case-sensitivity on a new Oracle database
    ClosedChange an existing case-sensitive Oracle database with Service Manager data to be case-insensitive
  • Set up a connection to Service Manager:

    Service Manager connects to the database through your RDBMS client. To set up the connection between the Service Manager application server and your RDBMS, know the name of the database and the login ID and password required to connect to the database server that you created above. The Service Manager initialization file, sm.ini, must be present in the Service Manager server RUN directory.

    To set up connectivity to your Oracle database:
    1. Install the Oracle client on your Service Manager server machine.

      Note: Service Managerrequires a 32-bit Oracle Client library, which can be found in the Oracle 64-bit Client installation directory or Oracle 32-bit Instant Client directory. Visit the Oracle site to download the proper Oracle client for the platform where you plan to run the Service Manager server.

    2. Configure a connection to the Oracle server in the tnsnames.ora file. Define the database name.
      • On UNIX systems, the tnsnames.ora file is located in $ORACLE_HOME/network/admin or can be specified using the TNS_ADMIN environment variable.
      • On Windows systems the tnsnames.ora file is located in the Oracle Home [%ORACLE_HOME%/network/admin] directory.
    3. For Oracle 11.1 or above only, disable ADR tracing by turning off the diag_adr_enabled parameter in the sqlnet.ora file: diag_adr_enabled=OFF. ADR tracing is enabled by default.

      Note: An Oracle bug ("Multi Threaded OCI Client Dumps Core After Reconnecting To Database") is triggered when ADR tracing is enabled. Once this bug is triggered, the Service Manager server will crash every time when setting up a connection to the Oracle server.

    4. Specify the name of the Oracle database connection in the sqldb parameter in the sm.ini file. You can do this after you install the Service Manager Server by running the Configuration tool and specifying the database name you provided in the tnsnames.ora file.
  • Set time zones for reporting:

    If you plan to report on Service Manager data using your RDBMS tools, set the sqltz parameter in the sm.ini file. This is an optional parameter that the Service Manager server uses to control the storing of date and time values in the RDBMS. This parameter defines the time zone to use as a base for all date and time values. The time zone is specified as the name of the time zone record in the Service Manager tzfile table. The default time zone is Greenwich/Universal (GMT). For more information about using the sqltz parameter, see the System Configuration Parameters topic in the Service Manager Help.

    Caution: If you use different time zone settings, the dates contained in reports made by your RDBMS utility may be inaccurate.

  • Set Oracle table spaces. Most tables on an Oracle server hold less than 50 KB of data. Service Manager sets the initial storage space size when creating the SQL tables. When manually creating a new Oracle instance, follow these guidelines:
    • Create the database with a block size of 8 KB or a multiple thereof.
    • Create a separate table space for the Service Manager data, and make this the default table space for the Service Manager user.
    • Set the TEMPORARY table space for the Service Manager user to an appropriate temporary table space.

 

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.