-
Back up your database before upgrade.
-
Login with the local administrator account.
-
Open a Command Prompt window as an administrator, with the %SMAT_DB_InstallFolder%\ as working directory.
-
Set ORACLE_HOME and ORACLE_SID.
-
Invoke SQL*Plus.
-
Connect as SYS.
-
Type shutdown immediate and press ENTER.
-
Type conn sys/<sys_password>@<SID> as sysdba, and press ENTER.
-
Type create pfile from spfile; and press ENTER.
-
Modify <ORACLE_HOME>\database\initSID.ora:
Change the parameter compatible from 12.2.0.1.0 to 18.6.0.0.0.
compatible=18.6.0.0.0
-
Save the changes.
-
Type create spfile from pfile; and press ENTER.
-
Type startup and press ENTER.
-
Execute tnsping to check if the database is available again.
If tnsping succeeds, you can continue with the next step.
-
Type @install_upgrade.sql and press ENTER to start the upgrade script.
-
Read the instructions on the screen.
-
Press ENTER to continue.
-
Enter your <SID> and press ENTER.
-
Enter the SYS password and press ENTER.
-
Enter the M_SYS password and press ENTER.
-
Press ENTER to start the upgrade process.
-
Press ENTER again.
The upgrade progress is shown in the SQL window.
-
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.
-
To allow Java access to local files, open a SQL*Plus session, and connect as SYS.
-
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.
The path must match the PDB_REPORT_DEST_DB setting entered on the A.60.04 DBA Settings screen in Smart Materials. If you do not know this setting, you can perform this step at any time later on.
-
Customer CIPs are saved to the installation_logs folder during upgrade. You may have to modify and re-apply these procedures to the new Smart Materials release.
-
The upgrade of your database is now finished and you can log on to your database.