800xA for MOD300 IM History Configuration
HI,
I have a question regarding IM History Configuration
I have an 800xA for MOD300 system at ver. 6.0.2
with 1195 IM history logs for and one message log with 4000000 event capacity
Attached you can see some screenshots of the Oracle Instance situation
I would like to know if it is possible to extend the table space by adding new .dbf file
using the instance wizard.
This is so especially for the History Runtime Indexes that has no more space over 32767 MB x file.
So the question is if it is possible extend tablespaces by adding file with the instance wizard,
and more in general which is the best way to size the history software in order to have the maximum
depth of online history trend data and minimum constraint due to maximum Oracle database table space size
Regards.
Paul
I have a question regarding IM History Configuration
I have an 800xA for MOD300 system at ver. 6.0.2
with 1195 IM history logs for and one message log with 4000000 event capacity
Attached you can see some screenshots of the Oracle Instance situation
I would like to know if it is possible to extend the table space by adding new .dbf file
using the instance wizard.
This is so especially for the History Runtime Indexes that has no more space over 32767 MB x file.
So the question is if it is possible extend tablespaces by adding file with the instance wizard,
and more in general which is the best way to size the history software in order to have the maximum
depth of online history trend data and minimum constraint due to maximum Oracle database table space size
Regards.
Paul
Asked 1 year ago
Answers
1
Paul,
Table space expansion is a standard feature of the Oracle Instance Wizard, and it allows for both the extension of existing table spaces, (up to the maximum per instance), and also for the use of additional files to extend the number of instances. I am including a document that combines these processes that are further detailed in the IM documentation. I hope that this answers your questions. One other point to make is that there is a command that can be run to provide you with a single document showing all the configurations of the Table Spaces in one concise text file so that you can more easily plan your work without having to scroll back and forth between popup windows.
Open a Command Prompt window in the IM node, (typically while logged in as the Service Account user), and perform the following:
...> hsDBMaint -space -d > C:\spcRpt.txt
The resulting text file will provide you with this information.
Please note that care should be taken not to utilize the C:\ drive(partition) to hold Oracle database files, (unless configured initially by the system installer), as if Table Spaces are configured on that drive, and they are allowed to Auto-Extend, you may cause the drive to fill to a point where it becomes unusable.
Regards,
Geof Ledin
Table space expansion is a standard feature of the Oracle Instance Wizard, and it allows for both the extension of existing table spaces, (up to the maximum per instance), and also for the use of additional files to extend the number of instances. I am including a document that combines these processes that are further detailed in the IM documentation. I hope that this answers your questions. One other point to make is that there is a command that can be run to provide you with a single document showing all the configurations of the Table Spaces in one concise text file so that you can more easily plan your work without having to scroll back and forth between popup windows.
Open a Command Prompt window in the IM node, (typically while logged in as the Service Account user), and perform the following:
...> hsDBMaint -space -d > C:\spcRpt.txt
The resulting text file will provide you with this information.
Please note that care should be taken not to utilize the C:\ drive(partition) to hold Oracle database files, (unless configured initially by the system installer), as if Table Spaces are configured on that drive, and they are allowed to Auto-Extend, you may cause the drive to fill to a point where it becomes unusable.
Regards,
Geof Ledin
0
Paul,
I agree with all Geof wrote. In your case you would to add a new file on drive D:\ since you are at the limit. Ideally, for a larger IM you should have different dedicated physical disks for the run time data and the indexes as well as another one for the "flat files". I have found this when building several larger IMs over the years and is in line with the manual recommends.
In your case you do not seem to have many logs and they only use about 95 Gbyte "Flat File" storage. This space will not increase when more data is stored, only when you add more trend data logs. Only a very small part of the trend data logs (sort of meta data) is stored in Oracle tables (History Configuration Data and History Configuration Indexes), the actual data is stored in the "Flat files", one for each log.
The Oracle tables History Runtime Data and History Runtime Indexes are used for storing the event data, i.e. that is where the Message Log stores its information. If either of these tables reach their maximum total storage limit events will no longer be stored in the Message Log. When more space is made available events will again be stored, and the Message Log will try and and "catch up" from the 800xA Event System as far back as it can.
I hope this has cleared some things up. If not, feel free to ask more questions.
Regards,
Lars Fermvall
I agree with all Geof wrote. In your case you would to add a new file on drive D:\ since you are at the limit. Ideally, for a larger IM you should have different dedicated physical disks for the run time data and the indexes as well as another one for the "flat files". I have found this when building several larger IMs over the years and is in line with the manual recommends.
In your case you do not seem to have many logs and they only use about 95 Gbyte "Flat File" storage. This space will not increase when more data is stored, only when you add more trend data logs. Only a very small part of the trend data logs (sort of meta data) is stored in Oracle tables (History Configuration Data and History Configuration Indexes), the actual data is stored in the "Flat files", one for each log.
The Oracle tables History Runtime Data and History Runtime Indexes are used for storing the event data, i.e. that is where the Message Log stores its information. If either of these tables reach their maximum total storage limit events will no longer be stored in the Message Log. When more space is made available events will again be stored, and the Message Log will try and and "catch up" from the 800xA Event System as far back as it can.
I hope this has cleared some things up. If not, feel free to ask more questions.
Regards,
Lars Fermvall
Answered 1 year ago
Add new comment