This topic provides information on migrating the Context Store data from version 3.7 to version 3.8 or higher.
You can use the upward and downward arrow keys on your keyboard to move to the required migration step while running the migration process.
Before you begin
Create a database.
Create a new schema.
Important:
You can skip steps 2, 3, 4, and 5 if the data in the old schema is already on the MS SQL server.
On the Windows PowerShell screen, ensure that the Create new schema step displays Completed.
To select Migrate data from old database, press Enter
STEP RESULT:
This step starts running a database connection test and analyzes the data for the migration.
After the test is complete, in the Would you like to continue with the database test field, type y.
ADDITIONAL INFORMATION:
Typing n displays the previous menu.
STEP RESULT:
The screen displays the details of the data, total space required, and the estimated time for the migration.
In the Would you like to start the data migration now field, type y to continue.
ADDITIONAL INFORMATION:
Typing n displays the main menu.
Wait for the migration process to continue.
When the screen displays that the migration is complete, press Enter to go back to the main menu.
Use the downward arrow key on your keyboard to move to the Exit option and press Enter.
ADDITIONAL INFORMATION:
The following three migration steps displayed on the screen are applicable only for Avaya Oceana®:
Note:
For a standalone Avaya Context Store using the Audit persistence type, there is no upgrade path . The stored date is not compatible with the Journey persistence type.
Migrate to new resurrect schema.
Migrate to new journey schema.
Remove old schema data.
To interrupt the migration process, press Ctrl+C.
ADDITIONAL INFORMATION:
To resume the migration, you can rerun the script.
Note:
Rollback is not required for resuming the migration.
