linux operating commands and unix operating commands

Article: How to XQuery Non-JDBC Sources from JDBC

 
Thread Tools Search this Thread
# 1  
Old 03-01-2011
Article: How to XQuery Non-JDBC Sources from JDBC

Learn to use XQuery from within JDBC code to access data in non-JDBC sources.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Shell Script for HDFS Ingestion Using JDBC

Peers, I was in process of building a script that connects to salesforce using jdbc and pull the data using spark and process in hive table. During this process I have encountered a problem where and variable assigned with hadoop command that list files in Azure Data lake is not parsing the... (2 Replies)
Discussion started by: jg355187
2 Replies

2. Shell Programming and Scripting

Connect to Oracle database with JDBC drivers.

Hi All, We are having LINUX server. I would like to connect to oracle database from server to with the help of shell script and execute a procedure. We dont have oracle installed to use sqlplus and connect to database. Do we have any command to connect to database using JDBC drivers. ... (1 Reply)
Discussion started by: Girish19
1 Replies

3. Ubuntu

JDBC Connection

Hi, I am using ubuntu os.I need some information about JDBC connection. 1.how to connect eclipse with apache tomcat server 2.I am using mysql database,how to to find the database location 3.How to set the classpath 4.How to connect Mysql with java using eclipse.I need step by step procedure... (1 Reply)
Discussion started by: snallusami
1 Replies

4. Shell Programming and Scripting

using jdbc:thin in bash

Hi I want to include in my script a test for DB connection with jdbc:thin connection string(not using tnsnames.ora) For example:... (3 Replies)
Discussion started by: gdan2000
3 Replies

5. Shell Programming and Scripting

Unix to Sql Server via JDBC

I am trying to connect SQL SERVER VIA JDCB. Following is something I tried and will appreciate any help what I am doing wrong Here's what I did, I tried several variations, but I keep getting this error: Exception in thread "main" java.sql.SQLException: Unable to connect. Invalid URL I... (1 Reply)
Discussion started by: cqldba
1 Replies

6. SuSE

postgresql-jdbc on Suse

Hi, I am writing a Java Swing application and want to add Embedded SQL to it. The application should interact with a PostgreSQL database running on my local machine. The compiler complains that it cannot find the org.postgresql package included in the code. I'm guessing the problem is that... (0 Replies)
Discussion started by: marina
0 Replies
Login or Register to Ask a Question
imqdbmgr(1M)						  System Administration Commands					      imqdbmgr(1M)

NAME
imqdbmgr - manage a plugged-in JDBC-compliant Message Queue data store SYNOPSIS
/usr/bin/imqdbmgr subcommand argument [ [option...]] /usr/bin/imqdbmgr -h | -help /usr/bin/imqdbmgr -v | -version DESCRIPTION
The imqdbmgr utility creates and manages a Java DataBase Connectivity (JDBC) compliant database used for Message Queue persistent storage. The database can be either embedded or external. To use a JDBC-compliant database (and the imdbmgr utility), you need to first set a number of JDBC-related properties in the broker instance configuration file. See the Sun Java System Message Queue Administrator's Guide for addi- tional information. imqdbmgr supports four management subcommands. These subcommands, and their corresponding arguments and options follow the imqdbmgr command on the command line. See USAGE and OPTIONS. The following subcommands are supported: create Create a Message Queue database schema. delete Delete Message Queue database tables in the current data store. recreate Delete Message Queue database tables and recreate Message Queue database schema in the curent data store. reset Reset the database table lock to allow other processes to access database tables. The imqdbmgr subcommands support the following arguments: all Indicates the subcommand applies to the data store, as well as the database tables. lck Indicates the subcommand applies to the database table lock. oldtbl Indicates the subcommand applies to an older version of the database tables. tbl Indicates the subcommand applies to the database tables only. OPTIONS
The following options are supported: -b brokerName Specify the broker instance name and corresponding instance configuration properties. If this option is not specified, the default broker instance is assumed. Use this option with the create, delete, recreate, or reset subcommands. -D property=value Set system property property to value. Use this option with the create, delete, recreate, or reset subcommands. -h | -help Display usage help. Execute nothing else on the command line. -p password Specify the database password. Use this option with the create, delete, recreate, or reset subcommands. -u userName Specify the database user name. Use this option with the create, delete, recreate, or reset subcommands. -v | -version Display version information. Execute nothing else on the command line. USAGE
The following subcommands and associated arguments are supported: create all Create a new embedded data store and Message Queue database schema for a specified or default broker instance. create tbl [-u userName] [-p password] Create Message Queue database schema in an existing data store for a specified or default broker instance. delete tbl [-u userName] [-p password] Delete Message Queue database tables in the current data store for a specified or default broker instance. delete oldtbl [-u userName] [-p password] Delete the earlier version of Message Queue database tables. Used after the data store has been automatically migrated to the current version of Message Queue. recreate tbl [-u userName] [-p password] Delete Message Queue database tables and recreate Message Queue database schema in the current data store for a specified or default broker instance. reset lck Reset the database table lock to allow other processes to access database tables. ENVIRONMENT VARIABLES
The following environment variables affect the execution of this command: IMQ_JAVAHOME Specify the Java 2 compatible runtime. When this environment variable is not set it defaults to /usr/j2se. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. FILES
/var/imq/instances/brokerName/dbstore Recommended directory in which to create an embedded database. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWiqu | +-----------------------------+-----------------------------+ SEE ALSO
imqadmin(1M), imqbrokerd(1M), imqcmd(1M), imqusermgr(1M), imqkeytool(1M), imqobjmgr(1M), attributes(5) Sun Java System Message Queue Administrator's Guide SunOS 5.11 29 Mar 2004 imqdbmgr(1M)