Error Code details
V-5-1-2353
Severity: Error 
Component: Volume Manager 
Message:
Cannot recover temp database Cannot recover temp database

 

Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2008-12-04 10:07:56 PST
Platform: Generic
Release: Generic
Content:
If you can reboot the system, do so. If you do not want to reboot, then use the following procedure.

    To correct the error without rebooting

  1. Ensure that no vxvol, vxplex, or vxsd processes are running.

    Use ps -e to search for such processes, and use kill to kill any that you find. You may have to run kill twice to make these processes go away. Killing utilities in this way may make it difficult to make administrative changes to some volumes until the system is rebooted.

  2. Recreate the temporary database files for all imported disk groups using the following command:

    # vxconfigd -x cleartempdir 2> /dev/console

    The vxvol, vxplex, and vxsd commands make use of these tempdb files to communicate locking information. If the file is cleared, then locking information can be lost. Without this locking information, two utilities can end up making incompatible changes to the configuration of a volume.

Solution 2 Vote: [Useful] [Not useful]
Last Modified: 2008-12-04 10:07:56 PST
Platform: AIX 6.1 (POWER), AIX 5.1 (POWER), AIX 5.2 (POWER), AIX 5.3 (POWER)
Release: Generic
Content:
This error can happen if you kill and restart vxconfigd, or if you disable and enable vxconfigd with vxdctl disable and vxdctl enable. The error indicates a failure related to reading the file /etc/vx/tempdb/group. This is a temporary file used to store information that is used when recovering the state of an earlier vxconfigd. The file is recreated on a reboot, so this error should never survive a reboot.

If you can reboot the system, do so. If you do not want to reboot, then use the following procedure.

    To correct the error without rebooting

  1. Ensure that no vxvol, vxplex, or vxsd processes are running.

    Use ps -e to search for such processes, and use kill to kill any that you find. You may have to run kill twice to make these processes go away. Killing utilities in this way may make it difficult to make administrative changes to some volumes until the system is rebooted.

  2. Recreate the temporary database files for all imported disk groups using the following command:

    # vxconfigd -x cleartempdir 2> /dev/console

    The vxvol, vxplex, and vxsd commands make use of these tempdb files to communicate locking information. If the file is cleared, then locking information can be lost. Without this locking information, two utilities can end up making incompatible changes to the configuration of a volume.

Solution 3 Vote: [Useful] [Not useful]
Last Modified: 2008-12-04 10:07:56 PST
Platform: HP-UX 11i v1 (IA-64/PA-RISC), HP-UX 11i v2 (IA-64/PA-RISC), HP-UX 11i v3 (IA-64/PA-RISC)
Release: Generic
Content:
This error can happen if you kill and restart vxconfigd, or if you disable and enable vxconfigd with vxdctl disable and vxdctl enable. The error indicates a failure related to reading the file /var/vxvm/tempdb/group. This is a temporary file used to store information that is used when recovering the state of an earlier vxconfigd. The file is recreated on a reboot, so this error should never survive a reboot.

If you can reboot the system, do so. If you do not want to reboot, then use the following procedure.

    To correct the error without rebooting

  1. Ensure that no vxvol, vxplex, or vxsd processes are running.

    Use ps -e to search for such processes, and use kill to kill any that you find. You may have to run kill twice to make these processes go away. Killing utilities in this way may make it difficult to make administrative changes to some volumes until the system is rebooted.

  2. Recreate the temporary database files for all imported disk groups using the following command:

    # vxconfigd -x cleartempdir 2> /dev/console

    The vxvol, vxplex, and vxsd commands make use of these tempdb files to communicate locking information. If the file is cleared, then locking information can be lost. Without this locking information, two utilities can end up making incompatible changes to the configuration of a volume.

Solution 4 Vote: [Useful] [Not useful]
Last Modified: 2008-12-04 10:07:56 PST
Platform: Red Hat Enterprise Linux 4 (x86-32), Red Hat Enterprise Linux 4 (IA-64), Red Hat Enterprise Linux 4 (x86-64), Red Hat Enterprise Linux 5 (x86-32), Red Hat Enterprise Linux 5 (x86-64), Red Hat Enterprise Linux 5 (POWER), SUSE Linux Enterprise Server 9 (x86-32), SUSE Linux Enterprise Server 9 (IA-64), SUSE Linux Enterprise Server 9 (x86-64), SUSE Linux Enterprise Server 10 (x86-32), SUSE Linux Enterprise Server 10 (IA-64), SUSE Linux Enterprise Server 10 (x86-64), SUSE Linux Enterprise Server 10 (POWER)
Release: Generic
Content:
This error can happen if you kill and restart vxconfigd, or if you disable and enable vxconfigd with vxdctl disable and vxdctl enable. The error indicates a failure related to reading the file /var/vxvm/tempdb/group. This is a temporary file used to store information that is used when recovering the state of an earlier vxconfigd. The file is recreated on a reboot, so this error should never survive a reboot.

If you can reboot the system, do so. If you do not want to reboot, then use the following procedure.

    To correct the error without rebooting

  1. Ensure that no vxvol, vxplex, or vxsd processes are running.

    Use ps -e to search for such processes, and use kill to kill any that you find. You may have to run kill twice to make these processes go away. Killing utilities in this way may make it difficult to make administrative changes to some volumes until the system is rebooted.

  2. Recreate the temporary database files for all imported disk groups using the following command:

    # vxconfigd -x cleartempdir 2> /dev/console

    The vxvol, vxplex, and vxsd commands make use of these tempdb files to communicate locking information. If the file is cleared, then locking information can be lost. Without this locking information, two utilities can end up making incompatible changes to the configuration of a volume.

Solution 5 Vote: [Useful] [Not useful]
Last Modified: 2008-12-04 10:07:56 PST
Platform: Solaris 10 (SPARC), Solaris 10 (x86-64)
Release: Generic
Content:
This error can happen if you kill and restart vxconfigd, or if you disable and enable vxconfigd with vxdctl disable and vxdctl enable. The error indicates a failure related to reading the file /var/vxvm/tempdb/group. This is a temporary file used to store information that is used when recovering the state of an earlier vxconfigd. The file is recreated on a reboot, so this error should never survive a reboot.

If you can reboot the system, do so. If you do not want to reboot, then use the following procedure.

    To correct the error without rebooting

  1. Ensure that no vxvol, vxplex, or vxsd processes are running.

    Use ps -e to search for such processes, and use kill to kill any that you find. You may have to run kill twice to make these processes go away. Killing utilities in this way may make it difficult to make administrative changes to some volumes until the system is rebooted.

  2. Recreate the temporary database files for all imported disk groups using the following command:

    # vxconfigd -x cleartempdir 2> /dev/console

    The vxvol, vxplex, and vxsd commands make use of these tempdb files to communicate locking information. If the file is cleared, then locking information can be lost. Without this locking information, two utilities can end up making incompatible changes to the configuration of a volume.

 

User solutions
No user solutions yet.

 

Read and accept Terms of Service