Loading...
 

Installation of ObjectStore

Installation of ObjectStore

Installation of ObjectStore

1. start setup

 InstOS001.jpg

2. next to the next mask

 InstOS002.jpg

3. enter user and company and press Next to go to the next screen

 InstOS003.jpg

4. next to the next mask

 InstOS004.jpg

5. select path to the license file of ObjectStore 2013 and click Next to go to the next screen

 InstOS005.jpg

6. select custom

 InstOS006.jpg

7. customers and AppsWH: Deselect everything except "ObjectStore DBMS" in the C++ interface and go to the next screen with Next

 InstOS007.jpg

BASIS: In addition to "C++ Interface", "Data Services Admin Serv" and "Java Interface" must be set. Afterwards with Next to the next mask.

 instOS1.JPG

8. activate "Both client and server" and press Next to go to the next mask

 InstOS008.jpg

9. go to the next mask with Next

 InstOS009.jpg

10. go to the next mask with Next

 InstOS010.jpg

11. server installation: select "Yes - change Server parameters" and press Next to go to the next screen (continue with 12)

 InstOS011.jpg

12.changing parameters using the example of "Authentication Required".

 InstOS012.jpg

13. enter "None" and confirm with OK

 InstOS013.jpg

14. this is repeated for the following parameters:









This description can be used to determine the values actually required.

15. activate "No - do not create RAWFS partitions" and press Next to go to the next screen

 InstOS014.jpg

16. activate "Yes - initialize the Server log file" and press Next to go to the next screen

 InstOS015.jpg

17. with Next to the next mask

 InstOS016.jpg

18. if this message does not appear, uninstall and reinstall ObjectStore 2013!

Otherwise press "OK".

 InstOS017.jpg

19. select "Yes - start the Server automatically" and press Next to move to the next screen

 InstOS018.jpg

20. select "Yes".

 InstOS019.jpg

21. finish to finish the installation

 InstOS020.jpg

Install patch (ObjectStore 2013)

In contrast to the previous ObjectStore versions, patches can be easily executed under ObjectStore 2013.

ObjectStore services

The services "ObjectStore Cache Manager R7.0" and ObjectStore Server R7.0" must be started. After the installation, these are set to "automatic" from ObjectStore 2013 and should keep this setting. With previous ObjectStore versions these services were set to "automatic (delayed)" after installation.

  • "automatic" -> When Windows is started, the services are started at the same time. The desktop may be displayed a little later.
  • "automatic (delayed)" -> When starting Windows, the services are not started immediately, but slightly delayed. The desktop may be displayed a little earlier. Discipline is required from the users, as ClassiX must not be started immediately, but only 3-5 minutes after the desktop has been displayed, until ClassiX can be started. Otherwise errors may occur and the ObjectStore Cache Manager may not be started as a service but as a process.

Firewall Settings

In the firewall, the following ports and programs must be enabled as "Incoming Rule":

  • Port 51025 and Port 51031
  • Program %SystemDrive%\ODI_2013.0_32Bit\OStore\bin\oscmgr6.exe
  • Program %SystemDrive%\ODI_2013.0_32Bit\OStore\bin\osserver.exe (is usually released automatically by ObjectStore)

Ports 51025 and 51031 must be enabled as "outgoing rule".

Without these settings in the firewall, the connection to the ObjectStore server may be lost. For more information, see here.

Notes on installation on a terminal server

Known problems:

It happened that a user could not start the application remotely because an ObjectStore error message was displayed.

 Error_file_mapping.JPG

This problem was resolved by adding the Remote Desktop Users user group to the local security policy for creating global objects:

Start>Programs>Administration>Local security policies
 instOS5.png

Security Settings...>Local Policies>Assign user rights: Creating global objects double click, then button "Add user or group" "Remote Desktop User
 instOS6.png

Possible errors and their remedies

Error description

ObjectStore Server cannot be started. Error message: "Missing license file", if started with -CON via the console, or alternatively found in the Windows Event Viewer.

Cause

The error only occurs since the update to OS2013 Update 6. Since this update the osserver seems to expect a copy of the license file under the path: %OS_ROOTDIR%\etc\license.txt

This is the license file that had to be specified during the ObjectStore installation.

Troubleshooting
Copy a copy of the ObjectStore license file to the appropriate path, then restart the service.

Error description

ObjectStore Server cannot be started. Error message: "C:\ODI_2013.0\osserver.log does not exist", if the server is started via -CON, or alternatively found in the Windows Event Viewer.

Cause
Unknown, only occurs after updating to ObjectStore-2013 Update 6
Troubleshooting

Start CMD and perform the following:

%OS_ROOTDIR%\bin\osserver.exe -CON -ReallocateLog

Then close the osserver with CTRL+C, close CMD and start the OSServer service.

Error description

ObjectStore cache manager and/or server are not accessible on the local computer (Windows Vista)

Example
In a DOS User Box, enter the following commands

c:\>oscmstat
Failed to communicate with Cache Manager on host "..."

c:\>ossvrping localhost
The sserver refused the connection
Attemp to connect to server host "..." failed
Possibly there is no server running.
(The original error message was: Could not establish network connection OpenEvent "Global\accept.server_client" failed: 2 (err_net_cant_connect)) (err_server_refused_connection)

Possible cause
  • Services are not running
  • On Windows Vista: UAC is enabled, services do not run as administrator
Troubleshooting
  • Switch off User Access Control
  • or: Set the environment variable OS_NETWORK as system variable, then restart the computer so that services and the following processes take over the settings:
    OS_NETWORK=O7NETTCP
    This solution is better from a user security point of view than switching off the UAC, but is slightly slower.
Another possible cause
The Windows Firewall blocks the port the client needs to send feedback to the ObjectStore Server
Troubleshooting
Port 51031 TCP must be enabled in the Client - Firewall settings (Firewall exceptions)
See Firewall Administration for details

If there are multiple network adapters (including virtual ones) ObjectStore may have connected to the wrong one

Error description

No connection to the database is established

Example
 error002.gif
Possible cause
The ObjectStore server is either not active or cannot be accessed via the network.
Troubleshooting
In a DOS-Box the command:

ping

enter. It returns the IP address of the server. If there is no answer here (time-out), the computer - on which the database server is running - is already unreachable in the network: Please create a connection first!

In a DOS-Box the command:

ossvrping

enter. This can be used to check whether the Objectstore database server is active. If it is not active, it must be started.

To increase the speed of finding the database server, you can edit the file \system32\ drivers\etc\hosts. with a text editor (e.g. NotePad) If none exists, create it (Attention: NO file extension, NotePad takes .Txt by default if no extension is given, therefore enter the concluding '.' when saving).

Insert the following line at the end:

Another possible cause
The Windows Firewall blocks the port the client needs to send feedback to the ObjectStore Server
Troubleshooting
Port 51031 TCP must be enabled in the Client - Firewall settings (Firewall exceptions)
See Firewall Administration for details
Another possible cause
The database is not located on a drive belonging to the server but is accessed via a linked drive (share).

Check whether the server name or IP address is specified in the error message, and compare it with the expected server. If the information does not match, the database is probably not "server-local" and is located on a share (e.g. NFS or Windows share).

Troubleshooting
  • Move the database to a drive belonging to the server.
  • Alternatively, a "remote" database can be connected via a locator file. This method is not recommended.
Another possible cause
If there are multiple network adapters (including virtual ones) ObjectStore may have connected to the wrong one
Troubleshooting
On the client, set the OS_BIND_INET environment variable to the IP address or host name

Error description

The schema database cannot be opened

Possible cause
The ObjectStore schema database (e.g. os_coll.adb) is local, but no server is installed
Troubleshooting
The schema database must be located on a computer running an ObjectStore server. The environment variable OS_SCHEMA_PATH must contain the path to these files (e.g. dbserver:c:\odi_7.1\ostore\bin).

Error description

After a short break a client has no connection to the database

Possible cause
The Windows Firewall blocks the port the client needs to send feedback to the ObjectStore Server
Troubleshooting
The port 51031/TCP and, if necessary, 51025/TCP must be enabled in the client firewall settings (firewall exceptions)
See Firewall Administration for details

Error description

Manual initialization of the transaction log fails:

Possible cause
The server parameter "Authentication required" is set to "None

You can list the server parameters with the command ossvrstat -parameters.

Troubleshooting
Start the setup and set the Authentication required in the server parameters to Default (this is "Name Password"). Then initialise the log again with osserver -con -i. After that you can set "Authentication required" to "None" again.