Home > rebuild db error > rebuild_db error calling dbunload

Rebuild_db Error Calling Dbunload

SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet During a 7.5 upgrade, ASA startup delays may cause a bpup failure and subsequent roll back to the previous version Article:000016631 Publish: Article URL:http://www.veritas.com/docs/000016631 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem The upgrade of the Sybase server is initially successful, but then encounters a problem and rolls back to the prior version of Sybase server and NetBackup. Error Message The installation log shows that the hostname is uppercase shortname, but that NetBackup is using a lowercase shortname.   05-07-2012,15:11:56 :  Starting Setup 05-07-2012,15:11:56 :  Performing installation on host: MYMASTER ...snip... 05-07-2012,15:22:41 :  Key: \SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config, Name: Client_Name, Value: mymaster ...snip... 05-07-2012,15:22:41 :  Key: \SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config, Name: Server, Value: mymaster, 05-07-2012,15:22:42 :  Key: \SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config, Name: EMMSERVER, Value: mymaster   The subsequent upgrade of the Sybase server uses the uppercase shortname.  The create_nbdb operation fails after 132 seconds, resulting in a rollback of the upgrade.   ...snip... 05-07-2012,15:23:37 :  Running command: "F:\VERITAS\NetBackup\bin\create_nbdb.exe" -db_server NB_MYMASTER -db_home "F:\VERITAS\NetBackupDB" -data "F:\VERITAS\\NetBackupDB\data" -force . 05-07-2012,15:23:37 :  Waiting for command: create_nbdb.exe ... 132 second delay ... 05-07-2012,15:25:49 :  Command returned status 1. 05-07-2012,15:25:49 :  ERROR: NetBackup Database Creation Failed! 05-07-2012,15:25:49 :  Review the log file in NetBackup\logs\nbdb for more information. 05-07-2012,15:25:49 :  Action ended 15:25:49: InstallFinalize. Return value 3. 05-0

administration utilities Unload utility (dbunload) Unloads a database into a SQL command file. Syntax dbunload [ options ] [ directory ] Option Description @data Read in options from the specified environment variable or configuration file. See Using configuration files. If you want to protect passwords or other information in the configuration file, you can use the File Hiding utility to obfuscate the contents of the configuration file. See https://www.veritas.com/support/en_US/article.000016631 File Hiding utility (dbfhide). -ac "keyword=value; ..." Connect to an existing database and reload the data directly into it, combining the operations of unloading a database and reloading the results into an existing database. This option is not supported on Windows Mobile. For example, you could create a new database using the http://dcx.sybase.com/1100/en/dbadmin_en11/dbunload.html Initialization utility, and then reload it using this option. This method is useful when you want to change initialization options. The following command (entered all on one line) loads a copy of the c:\mydata.db database into an existing database file named c:\mynewdata.db: dbunload -c "UID=DBA;PWD=sql;DBF=c:\mydata.db" -ac "UID=DBA;PWD=sql;DBF=c:\mynewdata.db" If the original database was created using version 9 or earlier of SQL Anywhere and the new database is not already running, you must provide a database server name in the -ac option. For example: dbunload -c "UID=DBA;PWD=sql;DBF=c:\mydata.db" -ac "UID=DBA;PWD=sql;DBF=c:\mynewdata.db;ENG=newserver" If you use this option, no interim copy of the data is created on disk, so do not specify an unload directory in the command. This provides greater security for your data. -an database Combine the operations of unloading a database, creating a new database, and loading the data using this option. This option is not supported on Windows Mobile or when rebuilding version 9 or earlie

20 日由admin123 回复 Problem The Symantec Private Branch Exchange service (pbx_exchange.exe) shows a steady increase in the Mem Usage Column in the Windows Task Manager. The increase is about 1 MB per http://www.kbeifen.com/?m=20120820 day and doesn’t depend on time and user activity. As a result Windows Nonpaged Pool was exhausting. Cause There is a memory leak in PBX version which is used by NetBackup 6.5.x. Solution The formal resolution for this issue is resolved in the following release: NetBackup 7.x 发表在NetBackup、企业备份 | 标签有PBX | 发表回复 NetBackup NBDB database upgrade failed to rebuild_db error locate Sybase libraries 发表于2012 年 8 月 20 日由admin123 回复 Problem Attemping to upgrade from NB6.5.3 directly to NB7.1GA. Upgrade process fails to load Sybase libraries, causing NBDB to fail to load, preventing the upgrade to 7.1 and ASA11 from completing. Error Snippet of STDOUT at upgrade: Database server is NB_HOSTNAME ld.so.1: dbping: fatal: libdblib11_r.so: open failed: No such file rebuild_db error calling or directory Killed NetBackup database already exists in /usr/openv/db/data/NBDB.db Making a copy of the existing database files in /usr/openv/db/staging Rebuilding the NetBackup database [NBDB]. This will take some time. ld.so.1: dbping: fatal: libdblib11_r.so: open failed: No such file or directory Killed ld.so.1: dbunload: fatal: libdbtool11_r.so: open failed: No such file or directory Killed Database [NBDB] can't be rebuilt. Unable to create/upgrade the NB database. Refer to the log file in /usr/openv/netbackup/logs/nbdb for more information. Rerun /usr/openv/netbackup/bin/install_bp when the problem has been resolved. nbdb log: 17:13:52.906 [19175] <4> pingDBServer: Entering. 17:13:52.907 [19175] <4> pingDBServer: Running . /usr/openv/db/vxdbms_env.sh && "/usr/openv/db/bin/dbping" -q -c "ENG=NB_airdbkupp1;LINKS=shmem,tcpip{PORT=13785}" 17:13:52.932 [19175] <16> NBDBsystem: System call failed with status: 35072 17:13:52.932 [19175] <16> pingDBServer: Database server [NB_HOSTNAME] not available. 17:13:52.933 [19175] <4> pingDBServer: Exiting. rc = 12 17:13:52.963 [19175] <4> rebuild_db: Running . /usr/openv/db/vxdbms_env.sh && /usr/openv/db/bin/dbunload -ar -c "UID=dba;PWD=******;DBF=/usr/openv/db/data/NBDB.db" -v -o "/usr/openv/db/log/dbunload.NBDB.log" 17:13:52.989 [19175] <16> NBDBsystem: System call failed with status: 35072 17:13:52.989 [19175] <16> rebuild_db: Error calling dbunload 17:13:52.989 [19175] <4> rebuild_db: Exiting. rc = 77 Environment Solaris 10 Master server, running NetBackup 6.5.3, attetmping t


Related content

No related pages.