This is a discussion on newbie: Administering DB2 from clients with oleDB connection within the DB2 forums, part of the Database Server Software category; --> Hello, We are making a program for benchmarking DB2 databases in C#.NET ( for a DB2 ESE V8.2 on ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello, We are making a program for benchmarking DB2 databases in C#.NET ( for a DB2 ESE V8.2 on SuSe 9 SLES). For this, we also want to request some basic information from the database: list database directory, list tables for schema dasusr1... Running the regular queries against the db is no problem, but when we want to run these commands, we get 'system error' in .NET. Now, I think we need to catalog the database on the client pc (where we are running DB2 Runtime Client on XP pro). Is this correct? thanx for the help Bert -- Message posted via DBMonster.com http://www.dbmonster.com/Uwe/Forums....m-db2/200505/1 |
| |||
| "Bert via DBMonster.com" <forum@nospam.DBMonster.com> wrote in message news:8ad8a8a0cb41414c80f0a405977bd929@DBMonster.co m... > Hello, > > We are making a program for benchmarking DB2 databases in C#.NET ( for a > DB2 ESE V8.2 on SuSe 9 SLES). > For this, we also want to request some basic information from the > database: > list database directory, list tables for schema dasusr1... > > Running the regular queries against the db is no problem, but when we want > to run these commands, we get 'system error' in .NET. > > Now, I think we need to catalog the database on the client pc (where we > are > running DB2 Runtime Client on XP pro). > Is this correct? No. You can also publish the database in Active Directory, which is easier. I also suspect that this isn't your problem. > > thanx for the help > > Bert > > -- > Message posted via DBMonster.com > http://www.dbmonster.com/Uwe/Forums....m-db2/200505/1 |
| |||
| We are not working with Active Directory or Domain controllers. Is there any other option to get this working? -- Message posted via http://www.dbmonster.com |
| |||
| or to at least narrow down the problem. Maybe I should reask my question. What is the procedure (in general) to administer DB2 from a .NET application running on XP Pro? I'm not asking for details, just a general guideline.. (altough details are welcome Thanks in advance Bert -- Message posted via http://www.dbmonster.com |
| |||
| Under the circumstances: .NET, but no domain, Linux server, XP client, there is little I can do to help you with your latest question. Open a support case with IBM. "Bert via DBMonster.com" <forum@DBMonster.com> wrote in message news:a896d5286418406a91d12a3fa8472476@DBMonster.co m... > or to at least narrow down the problem. > > Maybe I should reask my question. What is the procedure (in general) to > administer DB2 from a .NET application running on XP Pro? > I'm not asking for details, just a general guideline.. (altough details > are > welcome > > Thanks in advance > > Bert > > -- > Message posted via http://www.dbmonster.com |
| ||||
| Hi Bert; sounds like you are connecting and executing SQL just fine. The issue appears to be that oyu are issuing DB2 commands ("list database directory", etc) as is they were SQL statements - which they are not. I believe you either need to either write stored procs which use the admin API or if you can find what you need in the new SYSPROC table functions you can use those. Basically, you need to be running plain vanilla SQL from your client and you can do this in either of the 2 ways I described. Hope this helps. Pete H |
| Thread Tools | |
| Display Modes | |
|
|