Page History

This section includes the following topics:

• Renaming the Precise FocalPoint server
• Moving the Precise FocalPoint server
• Moving the PMDB FocalPoint to another server
• Moving the PMDB to another server

Anchor
RenamingthePreciseFocalPointserver RenamingthePreciseFocalPointserver

Renaming the Precise FocalPoint server

Using CLI you can rename the Precise FocalPoint server. This can be used, if due to IT requirements, you need to rename the Precise FocalPoint server.

Limitations

• If the FocalPoint server has instances or Collectors installed on it, you can’t rename it. The only exceptions to this, are the following agents:
  • Alerts InformPoint
  • Precise for SAP agent
• If you have a Collector other than the ones above, installed on the FocalPoint server, contact Customer Support for further assistance.
• If you have already installed updates on one of your components, verify with Customer Support whether you have to reapply these updates after performing the Move and Rename procedure.

Procedure

To rename the FocalPoint server

...

Table 13-1 Elements for Renaming the Precise FocalPoint server

Anchor
MovingthePreciseFocalPointserver MovingthePreciseFocalPointserver

Moving the Precise FocalPoint server

Using CLI you can move the Precise FocalPoint server. This can be used if, due to IT requirements, you need to move all Precise FocalPoints on the server to another server.

Limitations

• The instructions refer to moving all Precise components that are installed on the Precise FocalPoint server to another server. Partial moving, or moving components from a server other than the Precise FocalPoint server, is not supported. If you want to move only one FocalPoint, contact Customer Support.
• If the FocalPoint server has instances or collectors installed on it, you can’t move it. The only exceptions to this, are the following agents:
  • Alerts InformPoint
  • Precise for SAP agent
• If you have a Collector not from the list above installed on the FocalPoint server, contact Customer support for further assistance.
• Only the PMDB FocalPoint is handled; the PMDB is not moved during this procedure. To move the PMDB, see Moving the PMDB to another server.
• Datafiles in the Precise FocalPoint that were not loaded to the PMDB are lost.
• The server to which the Precise FocalPoint is moved should have the same characteristics as the original Precise FocalPoint server.
  • Identical operating system vendors.
  • Same operating system type. However, the version may be different. For example: A transition from Linux 6.2 to Linux 7.0 and vice versa is not supported, but a transition from Linux 7.0 to Linux 7.1 and vice versa is possible.
  • Same bit version. Moving components from 64-bit servers to 32-bit server, or vice versa, is not supported.
  • Same CPU model. Moving components from AMD CPU to ITANIUM CPU, or vice versa, is not supported.
• You cannot move the Precise framework and the product frameworks to a server that is already installed as part of your federation installation.
• If you have already installed updates on one of your components, verify with Customer Support whether you have to reapply these updates after performing the Move and Rename procedure.

Procedure

To move the FocalPoint server

...

Table 13-2 Elements for Moving the Precise FocalPoints server

...

...

...

...

...

...

...

...

...

...

...

...

...

Post-move adjustments and updates

After moving the FocalPoint server, you will need to make adjustments and updates for the following:•    Adjustment

• Adjustment for Precise for SAP FocalPoint and agents on the new server

...

• Updating SAP on the original server

Adjustment for Precise for SAP FocalPoint and agents on the new server

To adjust the Precise for SAP framework on the new server1.    Run

1. Run the following commands from the <precise_root> folder (to uninstall Precise for SAP FocalPoint services):
   products\sap\bin\pssp_install_fp.bat products\sap\bin\pssp_install_agents.bat IS1

...

1. Open the products\sap\cfg\IS1\agents-config.xml file and replace the original server's Precise root folder with the new server's Precise root folder in the following elements:

...

1. • homedir

...

1. • cfgdir

...

1. • logdir

...

1. • rfgdir
2. Start the agents on the new server.

Updating SAP on the original server

To update SAP on the original server•    Run

• Run the following commands from the <precise_root> folder to uninstall the Precise for SAP FocalPoint services:
  products\sap\bin\pssp_uninstall_fp.bat products\sap\bin\pssp_uninstall_agents.bat IS1

Verification

After moving the Precise FocalPoint’s server, perform the following verifications in the new installation:•    Check

• Check the agent’s status in Adminpoint

...

• Check that the Performance Warehouse processes are running and that data is loaded

...

• Check that data is displayed in the various products

Anchor
MovingthePMDBFocalPointtoanotherserver MovingthePMDBFocalPointtoanotherserver

Moving the PMDB FocalPoint to another server

Using CLI you can move the PMDB FocalPoint to a new server.

Limitations

...

• The new server should be installed (with BA) before the PMDB FocalPoint is moved.

...

• Only the PMDB FocalPoint is handled; the PMDB is not moved during this procedure. To move the PMDB, see Moving the PMDB to another server.

Procedure

To move the PMDB FocalPoint•    Run

• Run the following command from the main Precise FocalPoint server.
  Windows  

...

•  infra\bin\psin_cli.bat
                      -i3-user <user

...

• _

...

• name>
                      {-i3-encrypted-password

...

• <encrypted_

...

• password> | -i3-clear-password

...

• <clear_

...

• password>}
                      -action move-focal
                      -product PW
                      -old-server

...

• <old_server_

...

• name>
                      -new-server

...

• <new_server_

...

• name>
                      [-installation-cd-path

...

• <cd_

...

• path>]
  

...

• UNIX            ./infra/bin/psin_cli.sh
                      -i3-user <user

...

• _

...

• name>
                      {-i3-encrypted-password

...

• <encrypted_

...

• password> | -i3-clear-password

...

• <clear_

...

• password>}
                      -action move-focal
                      -product PW
                      -old-server

...

• <old_server_

...

• name>
                      -new-server

...

• <new_server_

...

• name>
                      [-installation-cd-path

...

• <cd_

...

• path>]

...

Table 13-3    Elements 3 Elements for Moving the PMDB FocalPoint to another serverElement    Description

...

...

...

...

...

...

...

...

Anchor
MovingthePMDBtoanotherserver MovingthePMDBtoanotherserver

Moving the PMDB to another server

Using CLI, you can move the PMDB to another server.NOTE    When

Limitations

...

• You can only move the PMDB. No agents are involved.

...

• You can only move to the same DBMS type (for example, Oracle to Oracle and SQL Server to SQL Server).
  However, you can move to another DBMS version.

  ...

  • • For an SQL Server based database, you must use the same authentication mode (SQL authentication or Windows OS Authentication), and the new database should have the same collation.

  ...

  • • For an Oracle database, you must use the same charset.

  For guidelines regarding export and import, see Examples for exporting and importing an SQL Server or Oracle based PMDB on page 142.

  Procedure

  To move the PMDB1.    Stop

  1. Stop all agents, including Precise Listeners and the Precise FocalPoint.

  ...

  1. Manually export the PMDB, and import it to the new DBMS. For an Oracle PMDB, export the PMDB tablespaces metadata also.

  ...

  1. Start the Precise FocalPoint.

  ...

  1. Run the CLI command on the main Precise FocalPoint server. The command updates the Precise registry with the related information.
     

  ...

  1. Windows   infra\bin\psin_cli.bat
                       -i3-user <user

  ...

  1. _

  ...

  1. name>
                       {-i3-encrypted-password

  ...

  1. <encrypted_

  ...

  1. password> | -i3-clear-password

  ...

  1. <clear_

  ...

  1. password>}
                       -action move-pw-db
                       -parameter <parameter

  ...

  1. _

  ...

  1. name>=

  ...

  1. <parameter_

  ...

  1. value>
     UNIX  

  ...

  1.        ./infra/bin/psin_cli.sh
                       -i3-user <user

  ...

  1. _

  ...

  1. name>
                       {-i3-encrypted-password

  ...

  1. <encrypted_

  ...

  1. password> | -i3-clear-password

  ...

  1. <clear_

  ...

  1. password>}
                       -action move-pw-db
                       -parameter <parameter

  ...

  1. _

  ...

  1. name>=

  ...

  1. <parameter_value>

  Info
  You need to specify only the parameters that were changed. For the list of parameters, see Installing the

  ...

  Precise framework.

  For example:

  For SQL Server in
  Windows:

            infra\bin\psin_cli.bat
            -i3-user admin -i3-clear-password admin
            -action move-pw-db -parameter dbms-instance=NEW_DATABASE1
            -parameter dbms-dba-user=sa
            -parameter dbms-dba-clear-password=sa
  For Oracle in
  UNIX:
            ./infra/bin/psin_cli.sh
            -i3-user admin -i3-clear-password admin
            -action move-pw-db -parameter dbms-
            server=new_poolhp6 -parameter dbms-instance=NEW_ORCL dbms-dba-user=SYSTEM dbms-dba-clear- password=MANAGER
  
  Table 13-4    Elements 4 Elements for Moving the PMDB to another server

  Element

  ...

  Description
  i3-

  ...

  user	See Authenticate to CLI Utility

  ...

  .

  i3-encrypted-

  ...

  password

  See Authenticate to CLI Utility

  ...

  .

  action

  ...

  Always move-pw-db Mandatory: Yes

  ...

  parameter

  The changed parameters. For more information about Performance Management DBMS related parameters, see Installing the Precise

  ...

  framework. Values: parameters in format name=value Mandatory: Yes

  Verification

  After moving the PMDB to another server, perform the following verifications in the new installation:•    Check

  • Check the agent’s status in Adminpoint

  ...

  • Check that the Performance Warehouse processes are running and that data is loaded

  ...

  • Check that data is displayed in the various products

  Anchor
  ExamplesforExportImport ExamplesforExportImport

  Examples for exporting and importing an SQL Server or Oracle based PMDB

  The following section provides examples of the export and import procedures for SQL Server and Oracle based PMDBs.

  Exporting and importing an SQL Server based PMDB

  To export an SQL Server based PMDB1.    Open

  1. Open the Microsoft SQL Server Management Studio.

  ...

  1. Right-click on the Performance Warehouse database.

  ...

  1. Select the Tasks > Back Up … option.

  ...

  1. Configure the backup file and click OK.

  ...

  1. Wait for confirmation of a successful export.

  To import an SQL Server based PMDB1.    Copy

  1. Copy the created backup file to the new server.

  ...

  1. Open the Microsoft SQL Server Management Studio on the new server.

  ...

  1. Right-click on Databases.

  ...

  1. Select Restore Database….

  ...

  1. In the "to database?" field, enter the previous database name.

  ...

  1. In the "from device" field, click on the ... (browse) button, and select the backup meda file.

  ...

  1. Select Add.

  ...

  1. Select the backup file.

  ...

  1. Click OK.

  ...

  1. Select the most recent backup.

  ...

  1. Click OK on the restore confirmation message.

  Exporting and importing an Oracle based PMDB

  When using Oracle as the PMDB repository, you can use the export and import utilities to move data. For more information, see http://wiki.oracle.com/page/Oracle+export+and+import+.

  Info

  ...

  These utilities are available under the <ORACLE_HOME>/bin folder.

  
  To export an Oracle based PMDB1.    Open

  1. Open a command line.

  ...

  1. Execute "exp" with the tablespaces’ parameter.

  ...

  1. Follow the instructions in the script (you can use most of default values).

  ...

  1. For "user to be exported", enter the PMDB user, for example: PRECISE_PMDB
     If error 942 occurs while using the export utility, execute the following as system user:
@c:\oracle\ora92\rdbms\admin\catexp.sql

  To import an Oracle based PMDB1.    Copy

  1. Copy the exported data to the new database.

  ...

  1. Open a command line in the new database.

  ...

  1. Execute the "imp‟ command and follow the script instructions.

  Precise. Performance intelligence from click to storage. Learn more > >

  ...

  
  

  Scroll Ignore
  scroll-pdf true scroll-office true scroll-chm true scroll-docbook true scroll-eclipsehelp true scroll-epub true scroll-html true
  Newtabfooter alias IDERA url http://www.idera.com  |  Newtabfooter alias Products url https://www.idera.com/productssolutions/sqlserver  |  Newtabfooter alias Purchase url https://www.idera.com/buynow/onlinestore  |  Newtabfooter alias Support url https://idera.secure.force.com/precise/  |  Newtabfooter alias Community url http://community.idera.com  |   Newtabfooter alias Resources url http://www.idera.com/resourcecentral  |  Newtabfooter alias About Us url http://www.idera.com/about/aboutus   |  Newtabfooter alias Legal url https://www.idera.com/legal/termsofuse

  ...