Smart Materials Upgrade to 8.4 - Intergraph Smart Materials - Version 10.2 - Installation & Upgrade - Hexagon

If your Smart Materials database is already on version 8.4 or higher, skip this section and continue with Smart Materials Upgrade to 10.0.

1. Back up your database before upgrade.

2. Login with the local administrator account.

3. Open a Command Prompt window as an administrator, with the%SMAT_DB_InstallFolder 8.4%\ as working directory.

4. Set ORACLE_HOME and ORACLE_SID.

5. Invoke SQL*Plus.

6. Connect as SYS.

7. Type shutdown immediate and press ENTER.

8. Type conn sys/<sys_password>@<SID> as sysdba and press ENTER.

9. Type create pfile from spfile; and press ENTER.

10. Modify <ORACLE_HOME>\database\initSID.ora, change the compatible parameter from 18.6.0.0.0 to 19.10.0.0.0:

    compatible=19.10.0.0.0

11. Save the changes.

12. Type create spfile from pfile; and press ENTER.

13. Type startup and press ENTER.

14. Execute tnsping to check if the database is available again.

    If tnsping succeeds, you can continue with the next step.

15. Edit variable.sql in %SMAT_DB_InstallFolder 8.4%\scripts directory, replace Oracle RDBMS Release and Oracle APEX Release sections with:

    REM Oracle RDBMS Release

    DEFINE min_oracle_version=1910000

    DEFINE min_oracle_compat=19100

    REM Oracle APEX Release

    DEFINE min_apex_version=20.2.0.00.20

    DEFINE min_apex_compat=2020.02.01

16. Type @install_upgrade.sql and press ENTER to start the upgrade script.

17. Read the instructions on the screen.

18. Press ENTER to continue.

19. Enter your <SID> and press ENTER.

20. Enter the SYS password and press ENTER.

21. Enter the M_SYS password and press ENTER.

22. Press ENTER to start the upgrade process.

23. Press ENTER again.

    The upgrade progress is shown in the SQL window.

24. When the upgrade is complete, check all log files for possible Oracle errors.

    The log files are located in the installation_logs and import folders. Logs have the following extensions: *.log, *.lst, and *.tmp. You can safely ignore all errors that refer to index creation with a specified indexed column combination that is already indexed. It is a best practice to keep these log files for later analysis. Do not use the same folder for more than one upgrade but copy it for each separate database upgrade.

25. To allow Java access to local files, open a SQL*Plus session, and connect as SYS.

26. Type the following command:

    EXEC dbms_java.grant_permission('M_SYS','java.io.FilePermission','<your

    PDB_REPORT_DEST_DB directory>','read,write,delete');

    Example:

    EXEC dbms_java.grant_permission('M_SYS','java.io.FilePermission','C:

    \oradata\SMAT\utl','read,write, delete');

    PL/SQL procedure successfully completed.