DBMaintPlus August 23, 2012. DBMaintPlus SQL Database Maintenance Utility for RB-ERP Version V9.3 and above Disclaimer The DBMaintPlus Utility is designed

DBMaintPlus

August 23, 2012

DBMaintPlusSQL Database Maintenance Utility for RB-ERP Version V9.3 and above

Disclaimer

The DBMaintPlus Utility is designed for use by staff familiar with RB-ERP and the SQL database versions of RB-ERP. Use of this program and the procedures included in this document are at the risk of the user. WorkWise is not responsible for misapplication or misinterpretation of the procedures included in this document.

DBMaintPlus and the procedures contained require that you have made sufficient backups and have a verified restore capability should issues arise. The end user of this utility and these procedures is responsible for such backups and verified restore capability.

This document contains procedures which will modify both the RB-ERP SQL Database and associated ISAM “cache” files on the RB-ERP Application Server. Care to insure data integrity is of the utmost priority in the use of this document.

DBMaintPlusSQL Database Maintenance Utility for RB-ERP Version V9.3 and above

RecommendationsIt is STRONGLY recommended that the use of this tool be done off-hours, with no users on the system.These procedures should only be done AFTER SUFFICIENT BACKUPS are made of the current RB-ERP SQL database and ISAM files. Multi-RB-ERP Environments - Caution !!Be VERY careful if multiple RB-ERP environments are on your servers. You must ensure you are referencing the correct environment when following any of the procedures in this document. Requirements for usage of this document:RB-ERP V9.3 or aboveDBMaintPlus.exe dated 8/3/2012 or better

DBMaintPlus Documentation

• Location on WW network:

DBMaintPlus Documentation

• Location on WW network:

DBMaintPlus on RB-ERP Server

DBMaintPlus on SQL Server

DBMaintPlusLearn by Examples

#1 Copy Existing RB-ERP Company (Schema) to New RB-ERP Company (Schema)

#2 Copy Existing RB-ERP Company (Schema) to Existing RB-ERP Company (Schema)

#3 Create New Company (Schema) ‘abc’

#4 Delete an Existing RB-ERP Company/Schema

#5 Refresh Test Environment W94 Data from Live Environment V94 Data

#6 Copy selected tables from one DB to another

DBMaintPlus Exercise #1

• Copy Existing RB-ERP Company (Schema) to New RB-ERP Company (Schema)– Make a copy of company 'tst' to non-existing 'new'– Steps starting on Page 8• Copy existing ISAM files from 'tst' to 'new'• Edit the EMS_REGISTRY.NEW file• Create the logical RB-ERP company 'new'• Verify “connection string” NEW TERM• Create xfODBC connection file for 'new'


• On SQL Server - Create schema for ‘new’– RB-ERP Server – DCM to Obtain DCM Version

• On SQL Server – Verify Linked Server Working• RB-ERP Server – DCM Tool to Update Schema• RB-ERP Server – DBMaintPlus – Copy Schema• RB-ERP Server – Delete/Create Cache Files• RB-ERP Server – Verify Sync’ed Cache Files• Additional tasks

– Background Scheduler and DC Services and process configurations as required


• Copy existing ISAM files from 'tst' to 'new'

Note – this will copy cache files etc from the DSQ folder! Bad news – it takes more time ! Good news – it verifies that there is enough space for the copies!

The “ED” application files are the ONLY ones that need to be copied. If you want to only copy “ED” files, use the command:

copy_tcmdata X:\tcm\W94_DATA0\ED tst new


• Copy existing ISAM files from 'tst' to 'new'


• Edit the EMS_REGISTRY.NEW file









Note – I always use: ‘spaceCMPspace’NOTE – Do the above replace using the

“Match Case” selection and do it twice: TST NEW and then tst new













CTRL_Z to finish !


• Create the logical RB-ERP company 'new'



Using Navigator Company Maintenance



Using Navigator Company Maintenance Select Add Company Code



Using Navigator Company Maintenance Select Add Company Code Select a blank entry (6) Enter ‘new’



Using Navigator Company Maintenance Select Add Company Code Select a blank entry (6) Enter ‘new’ 99% use (C)opy



Using Navigator Company Maintenance Select Add Company Code Select a blank entry (6) Enter ‘new’ 99% use (C)opy Warning Message - YES



Using Navigator Company Maintenance Select Add Company Code Select a blank entry (6) Enter ‘new’ 99% use (C)opy Warning Message – YES Company code to copy



Using Navigator Company Maintenance Select Add Company Code Select a blank entry (6) Enter ‘new’ 99% use (C)opy Warning Message – YES Company code to copy



Using Navigator Company Maintenance Select Change Company Name



Using Navigator Company Maintenance Select Change Company Name Enter ‘new’



Using Navigator Company Maintenance Select Change Company Name Enter ‘new’ Enter new company name



Using Navigator Company Maintenance Select Change Company Name Enter ‘new’ Enter new company name



Using Navigator Password/Device Maint



Using Navigator Password/Device Maint Add a new password



Using Navigator Password/Device Maint Add a new password SUPERPASS | new ‘M’ for all files ‘R’ for all files

Using Navigator Company Maintenance Connection String Maint


• Verify “connection string” NEW TERM


Using Navigator Company Maintenance Connection String Maint Enter new company ‘new’



Using Navigator Company Maintenance Connection String Maint Enter new company ‘new’ Hitting enter on field to chg will verify the string







SQL DB USERNAME | PW



SQL DB USERNAME | PW



SQL SERVER DSN NAME



SQL SERVER NAME



SQL DB NAME

• Create xfODBC connection file for 'new'


Copy ‘tst’ con file to ‘new’ new_W94.con

X:\var\tcm\connect



Edit ‘new’ con file



Replace ‘.tst’ with ‘.new‘


• On SQL Server - Create schema for ‘new’



SQL Server Name



SQL Server Name



SQL Server Name



SQL Server Name


• On SQL Server - Create schema for 'new'

SQL DB Name

Schema Code ‘new’

DCM Version




DCM Version


What DCM Version do I use ?

Where can I find out?


DCM Version


What DCM Version do I use ?

Where can I find out?

• RB-ERP Server – DCM to Obtain DCM Version

DCM Tool






Verify Environment

Verify Environment



Verify Environment

Verify Environment

Verify SQL Server

Verify SQL DB Name



Instance Name if Required






DCM Version


Create Schema – NOT UPGRADE SCHEMA

RB-ERP Server Name



xfODBC Connection File Name

Data used for creation of a Linked Server which allows access back to the RB-ERP Application Server for access to ISAM Files.

RB-ERP Server Name



xfODBC Connection File Name

Data used for creation of a Linked Server which allows access back to the RB-ERP Application Server for access to ISAM Files.





Progress logged here…

This step will take awhile !!



Done – Check for error messages


• On SQL Server – Verify Linked Server Working

Using SSMS Server Objects Linked Servers



Using SSMS Server Objects Linked Servers Locate new linked server Right-Click – Test



Using SSMS Server Objects Linked Servers Locate new linked server Right-Click – Test

DCM Tool


• RB-ERP Server – DCM Tool to Update Schema





Verify Environment

Verify Environment

Verify SQL Server

Verify SQL DB Name







Although the schema was created at V9.4, it needs to have any addendum updates and changes added to the vanilla V9.4 schema to be at the latest patch level.









Check EVERYONE FULL on the share W94_DATABASE permissions !



This step can take awhile !











This DCM process ran from 13:15 to 13:30 (15 minutes) on an empty schema!

Execution of this process on a LARGE data base against multiple schemas can take some time !!


• RB-ERP Server – DBMaintPlus – Copy Schema

And FINALLY we are actually going to “copy a

schema !!









Verify Correct Environment


Verify SQL Server Name


Verify SQL DB Name

Select source schema ‘tst’




Verify SQL DB Name Select destination schema ‘new’



There is a pause at this point ! Don’t panic – it is going to run !!















• RB-ERP Server – Delete/Create Cache Files

Change directory to DSQ

Delete existing ‘new’ cache




Delete existing ‘new’ cache

Build ‘new’ cache files



On a company with a HUGE amount of data, this can take a LONG TIME !!



Use dir *.ne* /p

Verify that all cache files got built – look for file 673.


• RB-ERP Server – Verify Sync’ed Cache Files

User is

qlvcount to verify



Check tcm_logger.log fileIn folder: X:\var\tcm\logger\logs



First ISQLVCOUNT

From the bottom find the first ISQLVCOUNT and search for “FAILED” to the bottom of the log file.



First ISQLVCOUNT

From the bottom find the first ISQLVCOUNT and search for “FAILED” to the bottom of the log file.




• Additional Tasks– Setup services for background processes as

required• RB-ERP Services

– Background Scheduler– DC Services – Including configuration within RB-ERP

» DCM1MA» DCSRVR


#1 Copy Existing RB-ERP Company (Schema) to New RB-ERP Company (Schema)

QUESTIONS ?


• Copy Existing RB-ERP Company (Schema) to Existing RB-ERP Company (Schema)– Make a copy of company 'tst' to existing 'new'– Steps starting on Page 32• Remove existing ISAM files for ‘new’• Copy existing ISAM files from 'tst' to 'new'• Edit the EMS_REGISTRY.NEW file• RB-ERP Server – DBMaintPlus – Copy Schema• RB-ERP Server – Delete/Create Cache Files• RB-ERP Server – Verify Sync’ed Cache Files


• Copy Existing RB-ERP Company (Schema) to Existing RB-ERP Company (Schema)– Make a copy of company 'tst' to existing 'new'– Steps starting on Page 32• Remove existing ISAM files for ‘new’• Copy existing ISAM files from 'tst' to 'new'• Edit the EMS_REGISTRY.NEW file• RB-ERP Server – DBMaintPlus – Copy Schema• RB-ERP Server – Delete/Create Cache Files• RB-ERP Server – Verify Sync’ed Cache Files


#2 Copy Existing RB-ERP Company (Schema) to Existing RB-ERP Company (Schema)

QUESTIONS ?


• Create New Company (Schema) ‘abc’– Create a new company code ‘abc'– Steps starting on Page 50• Create the logical RB-ERP company ‘abc'• Verify “connection string”• Create xfODBC connect file ‘abc_VXX.con’• Create base ISAM files (copy or initialize)

– DUT:UT_CURR_CODE.abc– DUT:EMS_REGISTRY.abc– DCM:TABLES.abc


• Set ‘abc’ Schema Device Table Entries to RDB• On SQL Server - Create schema for ‘abc’

– RB-ERP Server – DCM to Obtain DCM Version

• On SQL Server – Verify Linked Server Working• RB-ERP Server – DCM Tool to Update Schema• RB-ERP Server – Initialize all applications / files• RB-ERP Server – Create Cache Files• RB-ERP Server – Verify Sync’ed Cache Files• Additional tasks

– Background processes configurations as required


• Create New Company (Schema) ‘abc’– Create a new company code ‘abc'– Steps starting on Page 50• Create the logical RB-ERP company ‘abc'• Verify “connection string”• Create xfODBC connect file ‘abc_VXX.con’• Create base ISAM files (copy or initialize)

– DUT:UT_CURR_CODE.abc– DUT:EMS_REGISTRY.abc– DCM:TABLES.abc


• Set ‘abc’ Schema Device Table Entries to RDB• On SQL Server - Create schema for ‘abc’

– RB-ERP Server – DCM to Obtain DCM Version

• On SQL Server – Verify Linked Server Working• RB-ERP Server – DCM Tool to Update Schema• RB-ERP Server – Initialize all applications / files• RB-ERP Server – Create Cache Files• RB-ERP Server – Verify Sync’ed Cache Files• Additional tasks

– Background processes configurations as required

#3 Create New Company (Schema) ‘abc’

QUESTIONS ?



• Delete an Existing RB-ERP Company/Schema– DEM Company not needed – training / testing– Steps starting on Page 46• Delete the logical company ‘dem’ from RB-ERP

application• RB-ERP Server – Delete ‘dem’ ISAM / Cache• Delete the ‘dem’ schema using DBMaintPlus• Additional tasks

– Remove background processes as required


• Delete the logical RB-ERP company ‘dem'

Using Navigator Company Maintenance



Using Navigator Company Maintenance Select Delete Company Code



Using Navigator Company Maintenance Select Delete Company Code Locate ‘dem’ (2) Enter ‘2’



Using Navigator Company Maintenance Select Delete Company Code Locate ‘dem’ (2) Enter ‘2’ After checking for users, message of if you really want to do this appears.

Select YES – logical company is deleted.


• RB-ERP Server – Delete ‘dem’ ISAM / Cache Files

Change directory to DATA0

Delete ALL ISAMs for ‘dem’


• RB-ERP Server – Delete ‘dem’ ISAM / Cache Files


Delete ALL ISAMs for ‘dem’


• On SQL Server - Delete schema for ‘dem’





SQL Server Name


• On SQL Server - Delete schema for ‘dem'

SQL DB Name

Select Schema ‘dem’










#4 Delete an Existing RB-ERP Company/Schema

QUESTIONS ?



• Refresh Test Environment W94 Data from Live Environment V94 Data– Copy all company/schema data from V94 to W94 – Steps starting on Page 67

• Make a FULL backup of all data (static system)– V94 SQL DB V94_SQL_DB_BACKUP.BAK (Using SSMS)– V94_DATA0 V94_DATA0_COPY– V94_DATA1 V94_DATA1_COPY

• Note values in current W94 SQL DB ‘dbo.parameters’ table– Row 39 and Row 44

• Note W94 SQL DB users / schemas under security

DBMaintPlus Exercise #5• Optionally make backups first then delete

– Current W94 SQL DB– Current W94_DATA0 and W94_DATA1 – NOTE – you may want to save DC configuration ‘.DAT’ files in DUT

• Restore Data from V94 to W94– Using SSMS Restore SQL DB from Backup

» V94_SQL_DB_BACKUP.BAK SQL DB TCMW94– Copy / Replace

» V94_DATA0_COPY W94_DATA0» V94_DATA1_COPY W94_DATA1

– Set ‘dbo.parameters’ Row 39 and 44 back to noted values– Create users for all schemas in W94 SQL DB (DBMaintPlus)

• Verify xfODBC connection files for W94 environment

DBMaintPlus Exercise #5• Verify xfODBC connection files for W94 environment • Verify/correct connection strings for ALL schemas• Run DCM tool against all schemas in W94• Delete all cache files• Rebuild all cache files• Remove all non-standard triggers (DBMaintPlus)

– CRM– Others

• Additional Tasks– Restore Background processes as required – DC Config Files from DUT

• TEST - TEST - TEST - TEST– Make SURE you are hitting the correct SQL DB from the W94 Environment

» Make minor changes – verify using SSMS to see data changes

DBMaintPlus Exercise #5• Verify xfODBC connection files for W94 environment • Verify/correct connection strings for ALL schemas• Run DCM tool against all schemas in W94• Delete all cache files• Rebuild all cache files• Remove all non-standard triggers (DBMaintPlus)

– CRM– Others

• Additional Tasks– Restore Background processes as required – DC Config Files from DUT

• TEST - TEST - TEST - TEST– Make SURE you are hitting the correct SQL DB from the W94

Environment» Make minor changes – verify using SSMS to see data changes


• Backup of SQL DB using SSMS








• Copy origin V94_DATA0 and V94_DATA1


• Copy origin V94_DATA0 and V94_DATA1


• Note values in W94 SQL DB ‘dbo.parameters’– Row 39 and 44


• Note W94 SQL DB users/schemas under security


• Delete current W94 SQL DB










• Delete current W94_DATA0 and W94_DATA1 SQL DB


Delete ALL ISAMs


Delete ALL ISAMs


• Delete current W94_DATA0 and W94_DATA1


• Using SSMS Restore SQL DB from Backup– V94_SQL_DB_BACKUP.BAK SQL DB TCMW94








• Restore V94_DATA0 & V94_DATA1 copies to W94


• Using SSMS Restore SQL DB from Backup– Set ‘dbo.parameters’ Row 39 and 44 back to noted values


• Using SSMS Restore SQL DB from Backup– Set ‘dbo.parameters’ Row 39 and 44 back to noted values

Users are from TCM94_tenuser


• Using SSMS Restore SQL DB from Backup– Create users for all schemas in W94 SQL DB (DBMaintPlus)





SQL Server Name

SQL DB Name

Select ‘All Schemas’



Verify Environment



Verify RB-ERP App Server

Enter for each schema





WARNING Message about non-standard triggers appears!!

After DBMaintPlus Processing




• Run DCM tool against all schemas in W94

Verify Environment

Verify Environment

Verify SQL Server

Verify SQL DB Name


• Run DCM tool against all schemas in W94

• Verify “connection string” for ALL schemas




• RB-ERP Server – Delete/Create All Cache Files


Delete cache files !!

Build cache for ‘tst’

Continue to rebuild all cache files for all schemas !


• Remove Non-Standard Triggers (DBMaintPlus)




Verify SQL DB Name








Verify SQL DB Name









After Trigger Remove

#5 Refresh Test Environment W94 Data from Live Environment V94 Data

QUESTIONS ?



• Copy selected tables from one DB to another



Verify Environment



SQL Server Name

SQL DB Name

Select FROM ‘dem’



SQL Server Name

SQL DB Name

Select TO ‘tst’









NOTE – after copying tables:• Rebuild Z-Tables• Rebuild Cache Files

#6 Copy selected tables from one DB to another

QUESTIONS ?


RB-ERP – Background Processes

• Shop Floor Background scheduler• Data Collection (DC) Processes– DCM1MA– DCSRVR

• Two Steps– Setup of services– Configuration of DC Services

RB-ERP – Background Processes• Setup of Services – From RB-ERP Cmd Line– Starting up the services installer

Change dir to the ‘dcsf_services’ folder in the correct environment

• Setup of Services – From RB-ERP Cmd Line– Starting up the services installer


Enter ‘setup’


Possible problem – SETUP.EXE will not run

SETUP.EXE wants to install a new “srvany.exe” file. Current one is in use.

– Solution #1: Rename this file srvany.exe srvany.exe_old

– Solution #2: Stop all RB-ERP DC and B’grnd services




RB-ERP – Background Processes• Setup of Services – From RB-ERP Cmd Line– Starting up the services installer

• Setup of Services – From RB-ERP Cmd Line– What to setup ?


RB-ERP – Background Processes• Setup of Services – From RB-ERP Cmd Line– Background Scheduler


TCM Services User

TCM Services PW

Manual Startup


Company Code ‘tst’

• Setup of Services – From RB-ERP Cmd Line– Background Scheduler


RB-ERP – Background Processes• Setup of Services – From RB-ERP Cmd Line– Prompt for setup of another service?

• Setup of Services – From RB-ERP Cmd Line– Background Scheduler – Control Files


• Setup of Services – From RB-ERP Cmd Line– Background Scheduler – Control Files


• Setup of Services – From RB-ERP Cmd Line– Background Scheduler – Startup


RB-ERP Main Menu Manufacturing Shopfloor Control Other Functions Scheduler Startup



Options for startup orChecking current status.



Options for startup orChecking current status.

Current status shows all companies in the environment.



Selecting Start…

Shows configuration for the process.

Select OK to start…



Two DOS windows will appear as the bat files are processed.



Checking current status.

• Setup of Services – From RB-ERP Cmd Line– Background Scheduler – Shutdown


RB-ERP Main Menu Manufacturing Shopfloor Control Other Functions Scheduler Shutdown



Prompt for continue the shutdown is displayed.



Followed by a prompt for if you want an immediate shutdown.

• Setup of Services – From RB-ERP Cmd Line– Background Scheduler – Log Files



RB-ERP Background Scheduler

QUESTIONS ?

RB-ERP – Background Processes• Setup of Services – From RB-ERP Cmd Line– Prompt for setup of another service?

RB-ERP – Background Processes• Setup of Services – From RB-ERP Cmd Line– Data Collection

• Setup of Services – From RB-ERP Cmd Line– Data Collection


TCM Services User

Manual Startup

TCM Services PW

• Setup of Services – From RB-ERP Cmd Line– Data Collection – DCM1MA




Company Code ‘tst’



• Setup of Services – From RB-ERP Cmd Line– Prompt for another service to setup?


• Setup of Services – From RB-ERP Cmd Line– DCM1MA - Control Files


• Setup of Services – From RB-ERP Cmd Line– DCM1MA – Control Files


• Setup of Services – From RB-ERP Cmd Line– DCM1MA – EB-ERP Configuration


RB-ERP Main Menu Other Special Functions Application Mfg Dist Special Functions Data Collection DC SubSystems DCW Configuration Maintenance





It appears that DCM1MA configurations already exist?

How can that be?



The configurations came over from the V94 Environment that we moved into out W94 environment.

• Setup of Services – From RB-ERP Cmd Line– DCM1MA – EB-ERP Configuration File Location




Be VERY CAREFUL about checking configurations that were inherited from other environments!



The Host ID is from the old V94 environment !



MUST be changed to the correct W94 HOST ID !



If no configurations were in the environment, a prompt for new configurations would appeared.



Fill in the fields as appropriate for the new configuration.



On saving the configuration, the existing configurations now appear. To add new, hit ‘INSERT”, to remove hit ‘DELETE’.

• Setup of Services – From RB-ERP Cmd Line– DCM1MA – EB-ERP Startup


RB-ERP Main Menu Other Special Functions Application Mfg Dist Special Functions Data Collection DC Workstation Startup & Shutd



Options to check current status or START or STOP processes.



Show current status



Select process to start by Double-Click on the process.

Start DCM1MA process




Once selected an asterisk will appear on the process.






Start by hitting F1




Confirmation messages will appear .





Option to start now or at a later time will appear.




Two DOS windows will appear as the bat files are processed.




Show current status

• Setup of Services – From RB-ERP Cmd Line– DCM1MA – EB-ERP Shutdown


RB-ERP Main Menu Other Special Functions Application Mfg Dist Special Functions Data Collection DC Workstation Startup & Shutd



Options to check current status or START or STOP processes.



Select process to stop by Double-Click on the process.

Stop DCM1MA process



Select process to stop by Double-Click on the process.


Stop by hitting F1

Stop DCM1MA process




Stop DCM1MA process




Option to stop now or at a later time will appear.

Stop DCM1MA process

• Setup of Services – From RB-ERP Cmd Line– DC Services – Log Files



RB-ERP DCM1MA

QUESTIONS ?

Documents

DBMaintPlus August 23, 2012. DBMaintPlus SQL Database Maintenance Utility for RB-ERP Version V9.3 and above Disclaimer The DBMaintPlus Utility is designed