I go from all programs -> IBM DB2-> DBCOPY1(default)-> command line tools-> command editor
From the editor i write a simple query to create a table
CREATE TABLE student ( name CHAR(50) NOT NULL ,std_id INTEGER NOT NULL ,adress CHAR(50) ,contact CHAR(50) PRIMARY KEY (std_id) );
But showing .....
CREATE TABLE student ( name CHAR(50) NOT NULL ,std_id INTEGER NOT NULL ,adress CHAR(50) ,contact CHAR(50) PRIMARY KEY (std_id) ) DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL1024N A database connection does not exist. SQLSTATE=08003
SQL1024N A database connection does not exist.
There is no connection to a database. Other SQL statements cannot be processed unless an SQL CONNECT was previously executed.
The command cannot be processed.
If the error occurred when disconnecting from the database, continue processing. If the error occurred on another SQL statement, issue an SQL CONNECT statement and resubmit the command or statement.
sqlstate: 08003 what should i do for a data base and execute any query here ??
a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need. goodluck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Click Start, point to Settings, and then click Control Panel.
Double-click Add/Remove Programs, click Add New Programs, and then click CD or Floppy.
Locate the root folder of the Office source location, click Setup.exe, and then clickOpen.
Setup.exe is added to the command line that appears in the Open box of the Run Installation Program dialog box.
Click Finish to run Office Setup.
If requested, type your customer name and product key (CD key) information in the appropriate boxes, and then click Next.
Note The Next button is not available until you type a valid product key.
Accept the End User License Agreement, and then click Next.
Specify the location where you want to install Office, and then click Next.
On the Choose which applications for setup to install page, click Next.
If you click Choose detailed installation options for each application on theChoose which applications for setup to install page, and then click Next, the feature tree appears on the Choose installation options for all Office applications and tools page. Because Office Setup detects that you are using Terminal Services, the only installation states that are available are Not Available and Run from My Computer. By default, some features are set to Not Available. Do not change the installation states of these features to Run from My Computer, because you may experience problems with the Office programs that use these features.
Warning By default, some features are set to Not Available to make sure that there is optimum performance in a Terminal Server environment, including the elimination of unexpected errors. Do not change the installation states of these features to Run from My Computer.
Note If your Office source location is an administrative installation, Run from Networkis also displayed as an installation state.
On the Begin installation page, click Install.
When you receive a message that the installation completed successfully, click OK, clickNext, and then click Finish.
From the Windows Explorer, navigate to the directory where you installed Oracle Database XE, for example, c:\oraclexe.
Right-click the Oracle Database XE installation directory and from the menu, select Delete.
7.2.6 Step 6: Install and Run the Windows Installer CleanUp Utility
Run the Windows Installer CleanUp utility to remove the Windows
Installation configuration information for the Oracle Database XE
installation. You can download it from Microsoft at: http://support.microsoft.com/default.aspx?scid=kb;en-us;290301
he deinstallation completes, click Finish.
I, too, am a veteran of DOS to Windows conversions, in fact, I make my living at it. But I learned over a decade ago to get over the differences, like using Tab instead of Enter to move around the screen, and of course, the cursor shape.
If you want your converted program to be accepted by people who have never seen DOS, you need it to follow Windows UI conventions.
If you go to the Document Manager client when you click the file, it sounds like the file is a .gml, which is a DM document link.
If it was e.g. a Word-file, it would've been opened just like Windows normally handles that filetype.
But, if you want to open document directly from viewer, launch the viewer from the DM program folder, e.g. C:\program files\ibm\db2 document manager\dmviewer.exe
The solution was two-fold although I am not positive they are related. Download and install Service Pac 2, for Wordperfect Office X3. This file addresses Vista related issues and so may be crucial for programs originally written for XP. Once that file was installed, in QPro go to Tools/Settings/File Options and enter the path of the subdirectory you wish to open. Use a final "/". Perhaps, use another subdirectory for backups (the third line on the page). It worked fine.
hi, open Microsoft Office Document Imaging then opened the Tools menu, then Options. In the Options window, select the "Other" tab and clicked on the "Reset" button under Default Program.
Then, close Microsoft Office Document Imaging and open windows explorer, navigated to an "*.MDI" file, right clicked it and chose "open with" "choose a program" then browse to the Microsoft Office Document Imaging executable found in the Office folder (don't remember the exact location) and select that executable to open *.MDI files and check the box "always use this program to open this file type".
Now, finally, the "File" menu in Microsoft Office Document Imaging will work”
Perform following steps to recover sql server database:
Create a database with same size that you are trying to recover
Shutdown the SQL server
Swap old mdf file with new mdf file
Start the SQL server
Database may go in suspect
Set database in emergency mode
Run DBCC CHECKDB with repair_allow_data_loss to repair database
USE [master] GO ALTER DATABASE [RdmStoreInformation] SET EMERGENCY GO ALTER DATABASE [RdmStoreInformation] SET SINGLE_USER GO DBCC CHECKDB ([RdmStoreInformation], REPAIR_ALLOW_DATA_LOSS) GO ALTER DATABASE [RdmStoreInformation] SET MULTI_USER GO ALTER DATABASE [RdmStoreInformation] SET ONLINE
They are permanent procedures stored in the database that allow repeated execution of reusable SQL code. They are also compiled and stored in a cache repository to make their repeated execution more efficient.
The alternative to Stored Procedures is to use in-line queries "select * from table where field1 = value" hard-coded in your VB or C# application. This option though is less than ideal. Any change to the in-line query and you have to recompile the application.
The better way is to use a stored procedure, whose name doesn't change, and the parameters don't change. If the code has to change, then it's done in the stored procedure and recompiling the application isn't needed.