Scribd
Upload
72 views

Troubleshoot For Server

The document provides steps to troubleshoot a server that is not running or hanging by manually downloading and loading the database onto the server. It includes instructions to find the database files, extract and copy them to the correct folder, check the registry for the database ID, and create a text file to set the database version. It also describes how to create and clean a historian in SQL Server to resolve issues with the historian stopping the server loading.

Uploaded by

Gaurav Singh
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
72 views

Troubleshoot For Server

The document provides steps to troubleshoot a server that is not running or hanging by manually downloading and loading the database onto the server. It includes instructions to find the database files, extract and copy them to the correct folder, check the registry for the database ID, and create a text file to set the database version. It also describes how to create and clean a historian in SQL Server to resolve issues with the historian stopping the server loading.

Uploaded by

Gaurav Singh
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 40

SERVER NOT RUNNING

Server hanging or not running issues


• Due to more historian stored in “C” drive
• Not proper downloading database
• Server not having database in DBID1 or DBID2
CS loading stopping…..
Manual Database
Downloading to
Server
Find the DBID1 path
Inside the generated, DB find the .adb
file to servers
Manual loading Database in server

• Make .zip file from .adb file


• Extract the zip file
• Copy all extracted files and folders and paste
that inside the configuration > DBID1 >
S2KHMIconfiguration
When extracting zip file from .adb file

Continue next slide


…….,,,
Go to registry editor>HKEY_local
machine>Software>alstom….check current as DBID1 if
its having <Default> type DBID1 in current..
Find Vdbs…….
If Vdbs is “0” Type current DB version..
Go to S2KHMIConfiguration---Create
one notepad and rename it as Vdbs
Open notepad and type current DB
version
Final files and folders inside
s2kHMIconfiguration….
Open DB win and Run OI sever
HISTORIAN CREATION
AND CLEAN
Create Historian
Name it as <HISTORIAN> in database
name
Set the file growth 20 in percentage
and unrestricted file growth
Auto growth Historian log> In 10 MB and Restricted
file growth 5000MB
< Historian CREATED >
Delete HISTORIAN

OPEN SQL Server management studio


Right click on historian choose <delete>
< Delete historian >
CLEAN HISTORIAN LOG
Find the <cleanlogforsql> from this
path of DSAgile package
Run the Clean Historian Log for SQL
2005 version

• Run the Install clean log For SQL 2005.


Run the Clean Historian Log for SQL
2008 version

Open the file in note pad and delete


the following lines.
Run the Clean Historian Log for SQL
2008 version

• Run the Install clean log For SQL 2008.


Conform the clean historian job added
in SQL server
After connecting with server….
Find the clean log historian from SQL
server Agent
Job schedule properties
Then right click on <cleanloghistorian>
select start jobs.. It will shows success..
CHECKING ATTRIBUTES ON DATABASE
FOR SERVER ISSUES
Attributes…….
• MV data point transmission of event should
be “Percentage of full scale value”
• Profile table for MV point it should be “Archive
no logging”.
• For fault distance DP It should be Archive
Logging.
MV Data Point Setting

• Based on the following formula value will be


update in SAS
• Max*dead band variation/1000=vale updation
• Example:
Val features Max value=1000 ; Dead band=1
Change of 1 A value will be reported to SAS
MV attributes in DB……
Checking in OI Server
• In OISERVER attributes make it backup range
in 1 day also event and historic period in 1 day

You might also like