With the execution of DB2 SQL declaration, sometimes it returns statement execution information. This information comprises of SQL return code (SQLCODE) and SQLSTATE that sued to designates whether testimonial implementation was flourishing. Some SQL returns rule are offered by DB2 for I/O system that can be puzzled and then frequently orientation handbooks are not obtained or shut at hand while you actually required them. Sometimes you may get also get an error called SQL2036N due to some reason. BACKUP, RESTORE or LOAD will fail with SQL2036N when the path is mapped as remote drive. To know in brief about this error and how to fix this SQL error, you can follow the below post.
“While performing the Db2 move load-replace continues the “restore” from the previous post, I was failed once more. However, this time I got the error code SQL2036N which stated that the “the path for the file or device path/device is not valid” and after that I got another error which stated the message as “File I/O error occurred”. Do you have any idea why IBM Db2 did gave this kind of misleading error message and this error can be fixed with some manual methods. I am a logged in as user ‘root’ but the db2move command simply seem to tell another DB2 process to load the import files and this is generally a privilege separated process that cannot be opened the directory that used to contain my*.ixf files.”
Symptoms of SQL2036N Error:
When your db2 file will get infected with this error, then you may see that these error will be thrown when backup command is run:
- SQL2036N The path for the file or device “<F:\>” is not valid.”
- $db2 backup db sample online to F:
You may Also Like: DB2 SQL ERROR CODES AND SOLUTIONS
Causes of SQL2036N Error:
Some of the causes for getting this error in Db2 are as follows:
Backup, Restore and Load operations are performed specifying the network instead of completely qualified Universal Naming Convention (UNC) name.
How to Fix SQL2036N Error in DB2 File:
In order to resolve SQL2036N error, you can create a virtual hard disk in Windows so that you can see a network as local drive. Virtual Hard Disks (VHD) are a file type that used to act like a hard disk. However, by simply mounting a VHD, you can easily copy files to and from the virtual disk. However, you can also create a VHD from the Disk Management snap-in or you the command line. After creating the VHD, you should attach it and then format it before you can use it, exactly like a physical partition.
You May Also Like: How to Fix SQL0293N Error in DB2 database
In order to do, from the Disk Management console, you can follow the below steps:
- Right-click Disk Management and the simply click Create VHD, follow the instructions that appear on the screen.
- Now right-click the new disk and then simply click Initialize Disk and then click OK.
- After the above steps, there is a need to right-click the new disk and then click New Simple Volume and then follow the instructions that appear on the screen.
Now the new virtual disk is ready to be used just exactly like any other disk.
Or you have to choose one of the supported options which are:
– A device (for backups to tape)
– A directory (for backups to disk)
– Another vendor’s server
– A Tivoli® Storage Manager (TSM) server
Please check the DeveloperWorld technical Tips: “Create a DB2 backup on a Windows shared folder” for additional issue resolution steps.
You May Also Like: Recovering DB2 Database Post “SQL0980C a disk error occurred…” Error
Ultimate Solution to Fix SQL2036N in DB2 File:
After performing the above fixing solution, if you are still unable to fix your Db2 file which was affected due to getting SQL2036N error then you should try some other solution. In this case, you can also make use of DB2 File Repair Tool. This tool has the capability to fix any SQL error with an ease. The steps involved in the fixing issue of the DB2 file errors using this tool, are so easy that anyone can easily use it without nay technical help.
Steps to Fix SQL2036N Error in DB2 File:
Step 1: Install and launch DB2 File Repair tool. It will provide two options to repair db2 file, first option is if database is attached to DB2, then you can choose option ‘Repair the database stored at default location‘, and if database is not joined to DB2 then choose manual database selection.
Step 2: It will provide you the list of database attached to DB2. Select the particular database you want to repair and recover corresponding database objects.
Step 3: In this step this tool provide the list of recoverable database files. You can see the preview by clicking on it.
Step 4: Give the path location for the recoverable database and its object to be saved. Click on ‘Ok’ button.
With the above steps, you will be easily able to repair corrupted or damaged Db2 database with Db2 File Repair Tool without any hassle.