Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  3. IT Analytics Help
  5. Section XVI. System Administration
  7. Backing Up and Restoring Data
  9. Import the Oracle database

Import the Oracle database

Caution:

The following process deletes your existing IT Analytics database. Before you try to import the Oracle Database, verify you have no other recovery options and you have a valid database export. Contact Cohesity Support.

Some common problems include:

  • Importing unsuccessful backups. Ensure that your backups were successful before you accidentally import old data.

  • Importing more than what you need. Do not restore the entire database or import all database tables if you only need to restore one database table. Import only what you need.

Note:

Before restoring user objects, stop the Tomcat and Portal processes.

See Starting and stopping portal server software.

Database Import (Linux)

Prerequisites:

  • To import the latest successful export of the Oracle database, the database user Aptare user must have access to the export files stored in the /opt/aptare/database/tools directory.

  • The Oracle user must have read and execute privileges on these files before starting the database export.

  1. Log into the Linux database server and switch to user Aptare.

  2. Place the export file aptare_scdb.exp in the /tmp directory.

    If you have a different preferred directory (for example, /new_directory_path), then place aptare_scdb.exp in your preferred directory (/new_directory_path). Subsequently, change the path for the creation of directory from /tmp to the new directory (new_directory_path) in the /opt/aptare/database/tools/drop_users_linux.sql file.

    Note:

    You can also use /opt/aptare/ or /opt/aptare/oracle/rdbms/log/ directories.

  3. Place the aptare.ks file in the /tmp directory.

    Note:

    This step is required only if database is exported from an IT Analytics version of 10.5 or above.

  4. Place the aptare_external_password.properties file in the /tmp directory.

    Note:

    This step is required only if database is exported from an IT Analytics version 11.0 or above.

  5. Stop all Oracle and APTARE services as a root user: 

    /opt/aptare/bin/aptare stop

  6. Copy /opt/aptare/portalconf/master_data_keys.jceks file from source IT Analytics virtual machine to target IT Analytics virtual machine to same path.

  7. Start Oracle services as the root user:

    /opt/aptare/bin/oracle start

  8. Verify the Oracle Listener is running.

    /opt/aptare/bin/aptare status

  9. Run the following command: 

    chmod +x /opt/aptare/database/tools/import_database_template.sh

  10. Run the script import_database_template.sh as Aptare user. 

    /opt/aptare/database/tools/import_database_template.sh

  11. After successful completion, the data pump export file aptare_scdb.exp is saved on the Linux database server in the /tmp directory.

The import_database_template.sh script, unlocks Portal user, grants privileges, and validates the packages after the completion of the import, so they are not required to be run manually. The scripts also address the compilation warnings for the packages that follow.

The import log - import_scdb.log is located in the /tmp directory.

  1. Check the log file for compilation warnings for the packages:

    • view apt_v_solution_history_log

    • cmv_adaptor_pkg

    • avm_common_pkg

    • sdk_common_pkg

    • load_package

    • common_package

    • util

    These compilation warnings are addressed by the script itself and no action is required from the user.

    Note:

    If you are importing a database from version 10.4, upgrade the portal after the import to a 10.5 build.

  2. This step is required only if you are exporting the database from IT Analytics version 10.5 or above. Run the following commands to copy the aptare.ks file to datarcvrconf folder.

    cp /tmp/aptare.ks /opt/aptare/datarcvrconf/
chown aptare:tomcat /opt/aptare/datarcvrconf/aptare.ks
chmod 660 /opt/aptare/datarcvrconf/aptare.ks

  3. The encrypted information in portal.properties and datararcvrproperties.xml files must be replaced after the aptare.ks file has been copied to the portal. The information is re-encrypted when the portal services are restarted. The following modifications are required for both the files.

    Modification required for portal.properties file

    • Edit /opt/aptare/portalconf/portal.properties file

    • Remove all the characters following the first "=" on the lines containing db.password.encrypted and db.ro_user_password.encrypted

    • Specify the passwords for both users in the relevant lines

      Note:

      The db.user and db.ro_user information shown is below is for a default installation. Adjust the blank entries to match your environment. These will be re-encrypted when the portal services are restarted.

      #Database connection
db.driver=oracle.jdbc.driver.OracleDriver
db.url=jdbc:oracle:thin:@//localhost:1521/scdb
db.user=portal
db.password=portal
db.password.encrypted=
db.connection.max=75
db.connection.min=25
db.connection.expiration=30
db.ro_user=aptare_ro
db.ro_user_password=aptaresoftware123
db.ro_user_password.encrypted=

    Modification required for datararcvrproperties.xml file

    • Edit the datasource section of /opt/aptare/datarcvrconf/datrarcvrproperties.xml file

    • Clear the encrypted values for UserId, Password, ro_user, and ro_password

      Note:

      The UserId and ro_user information shown is for a default installation. Clear the text entries to match your environment. These will be re-encrypted when the portal services are restarted.

      <dataSource>
        <Driver>oracle.jdbc.driver.OracleDriver</Driver>
        <URL>jdbc:oracle:thin:@//localhost:1521/scdb</URL>
        <UserId>portal<=/UserId>
        <Password>portal</Password>
        <oracle_service_name>scdb</oracle_service_name>
        <ro_user>aptare_ro</ro_user>
        <ro_password>aptaresoftware123</ro_password>
        <MaxConnections>150</MaxConnections>
        <MinConnections>5</MinConnections>
        <ConnExpirationTime>5</ConnExpirationTime>
    </dataSource>

  4. This step is required only if you are exporting the database from IT Analytics version 11.0 or above. Execute the following commands to copy the file aptare_external_password.properties to datarcvrconf directory.

    cp /tmp/aptare_external_password.properties /opt/aptare/datarcvrconf/
chown aptare:tomcat /opt/aptare/datarcvrconf/aptare_external_password.properties
chmod 660 /opt/aptare/datarcvrconf/aptare_external_password.properties

  5. Run updateUser.sh to change the password of the application account. For example, to change the password for the admin123 application user, run updateUser.sh admin123 <newPassword>

  6. Restart all Oracle and APTARE services by running them from the root user: 

    /opt/aptare/bin/aptare restart

  7. If the Portal is deployed at a custom path (other than the default path : /opt/aptare), update the system parameter as follows:

    • Login to the Portal host as root user and run:

      su - aptare
cd /customPath/aptare/database/tools

    • Login to SQL Plus as a Portal user and substitute pwd with your password 

      sqlplus portal/pwd@<ServiceName>
@update_system_parameter.sql

    • Enter the custom installation path of the Portal, when you prompted as:

      "Enter value for input_path:"

      Example: If you have the Portal deployed under /<CustomPath>/aptare/ directory, provide the input path as /<CustomPath>/ while importing the database on the same host where the Portal is installed.

  8. Log into the Portal using the application account.

Database Import (Windows)

To import the latest successful export of the Oracle database, the database user Aptare user must have access to the export files stored in the directory:

c:\opt\oracle\database\tools

Verify the Oracle user has read and execute privileges on these files before starting the database export.

  1. Log into the Windows database server as a user who is a member of the ORA_DBA group.

  2. Place the export file aptare_scdb.exp in the directory:

    C:\opt\oracle\logs

  3. The encrypted information in portal.properties and datararcvrproperties.xml files must be replaced after the aptare.ks file has been copied to the portal. The information is re-encrypted when the portal services are restarted. The following modifications are required for both the files.

    Modification required for portal.properties file

    • Edit c:\opt\aptare\portalconf\portal.properties file

    • Remove all the characters following the first "=" on the lines containing db.password.encrypted and db.ro_user_password.encrypted

    • Specify the passwords for both users in the relevant lines

      Note:

      The db.user and db.ro_user information shown is below is for a default installation. Adjust the blank entries to match your environment. These will be re-encrypted when the portal services are restarted.

      #Database connection
db.driver=oracle.jdbc.driver.OracleDriver
db.url=jdbc:oracle:thin:@//localhost:1521/scdb
db.user=portal
db.password=portal
db.password.encrypted=
db.connection.max=75
db.connection.min=25
db.connection.expiration=30
db.ro_user=aptare_ro
db.ro_user_password=aptaresoftware123
db.ro_user_password.encrypted=

    Modification required for datararcvrproperties.xml file

    • Edit the datasource section of c:\opt\aptare\datarcvrconf\datrarcvrproperties.xml file

    • Clear the encrypted values for UserId, Password, ro_user, and ro_password

      Note:

      The UserId and ro_user information shown is for a default installation. Clear the text entries to match your environment. These will be re-encrypted when the portal services are restarted.

      <dataSource>
        <Driver>oracle.jdbc.driver.OracleDriver</Driver>
        <URL>jdbc:oracle:thin:@//localhost:1521/scdb</URL>
        <UserId>portal<=/UserId>
        <Password>portal</Password>
        <oracle_service_name>scdb</oracle_service_name>
        <ro_user>aptare_ro</ro_user>
        <ro_password>aptaresoftware123</ro_password>
        <MaxConnections>150</MaxConnections>
        <MinConnections>5</MinConnections>
        <ConnExpirationTime>5</ConnExpirationTime>
    </dataSource>

  4. Place the aptare.ks file in the C:\opt\oracle\logs folder.

    Note:

    This step is required only if database is exported from an IT Analytics version of 10.5 or above.

  5. Place the aptare_external_password.properties file in the c:\opt\oracle\logs folder.

    Note:

    This step is required only if database is exported from an IT Analytics version 11.0 or above.

  6. Stop all Oracle and Aptare services using stopAllServices from the Windows Services tab.

  7. Copy C:/opt/aptare/portalconf/master_data_keys.jceks file from source IT Analytics virtual machine to target IT Analytics virtual machine to same path.

  8. Verify the Oracle TNS Listener is running and start OracleServicescdb from the Windows Services tab.

  9. From the command prompt, run the script import_database_template.bat by executing the command: 

    c:\opt\oracle\database\tools\import_database_template.bat

  10. After successful completion of the import, run Startallservices from the Windows Services tab.

The import_database_template.bat script, unlocks Portal user, grants privileges, and validates the packages after the completion of import, so they are not required to be run manually. The scripts also address compilation warnings for the packages that follow.

The import log import_scdb.log is located c:\opt\aptare\oracle\logs.

  1. Check the log file for compilation warnings for the packages:

    • view apt_v_solution_history_log

    • cmv_adaptor_pkg

    • avm_common_pkg

    • sdk_common_pkg

    • load_package

    • common_package

    • util

    These compilation warnings are addressed by the script itself and no action is required from the user.

    Note:

    If you are importing a database from version 10.4, upgrade the portal after the import to a 10.5 build.

  2. Copy the saved file c:\opt\oracle\logs\aptare.ks to c:\opt\aptare\datarcvrconf folder. Ensure that the file is owned by IT Analytics user and has appropriate Read and Write access to the copied file.

    Note:

    This step is required only if database is exported from an IT Analytics version of 10.5 or above.

  3. Copy the saved file c:\opt\oracle\logs\aptare_external_password.properties to c:\opt\aptare\datarcvrconf folder. Ensure that the file is owned by IT Analytics user and has appropriate Read and Write access to the copied file.

    Note:

    This step is required only if database is exported from an IT Analytics version 11.0 or above.

  4. Run startAllServices using the Windows Services tab.

  5. Run updateuser.bat to change the password of the application account. For example, to change the password for the admin123 application user, run: updateuser.bat admin123 newPassword

  6. Log into the portal Application using the application account.

Restoring When a Cold Backup is Not Available

If you do not have a successful cold backup of your Oracle database, take the following steps to recover your IT Analytics Oracle database. Refer to the Installation and Upgrade Guides for complete details about re-installing the binaries and the database schema. Contact Support for assistance.

  1. Re-install the Oracle binaries.

  2. Re-install the database schema.

  3. Import the latest successful export of your Oracle database to restore the Portal user objects.

    See Import the Oracle database.

Feedback

Was this page helpful?
Previous

Restoring the IT Analytics system

Next

Manual steps for database import / export using data pump

Feedback

Was this page helpful?