Coba baca artikel dibawah ini saya dapat dari orafaq.com, saya sudah pernah
mencobanya dan berhasil.
Regards,
Burghan
====================
Access MS SQL Server tables from Oracle 9i
For the tables to be accessed we can use the generic connectivity. This is
using the hsodbc that is heterogenous Connectivity Drivers. The procedure is
here which we have created as a white paper. Please go step by step
1. CREATING THE SYSTEMDSN THROUGH THE DATASOURCE:-
The following procedure enables you to define a system DSN in the
Windows98/NT/2000/2000/serverXP ODBC Data Source Administrator,
1.1. From the Start menu, choose Settings > Control Panel and select the ODBC
icon. If it is in the windows 98. OR 1.1. If it is in windows NT/2000/XP
then goto the Start menu, choose Settings > Control
Panel and select the Administrator tools and then select the Data Sources
(ODBC).
1.2. Select the system DSN tab to display the system data sources.
1.3. Click Add.
1.4. From the list of installed ODBC drivers, select the name of the driver
that the
data source will use. For example, select SQL Server.
1.5. Click Finish.
1.6. Enter a name for the DSN and an optional description. Enter other
information
depending on the ODBC driver. For example, for SQL Server enter the SQL
Server machine. Press Next.
Note :- The name entered for the DSN must match the value of the
parameter HS_FDS_CONNECT_INFO that will be specified in initHS_SID.ora.
1.7. Then select the option (With SQL Server authentication using login ID and
password
entered by the user)
1.8. Then select the check box (Connect to SQL server to obtain default
settings for the
additional configuration options).
1.9. Now in the Text Box (Login ID: ) type the MS-SQL server login and in the
Text Box
of (Password: ) type the Password of the MS-SQL server user’s password.
Then press Next.
Note :- Every time this user will be used in order to connect to MS-SQL
server.
And tables available in this user’s schema will be available to query.
So no need of
giving the user and password again and again to connect to the database
of MSSQL
server.
1.10. select the check box (Change the default database to) then it will show
that
particular users database which you have previously mentioned in point
1.9 above.
Select that database from the List Of Values (LOV). Then click next and
then Finish.
1.11. Then the ODBC Microsoft SQL Server Setup window will be displayed. Here
check
the connection by pressing the test button which checks the
connectivity to
MS-SQL Server with the authentication of User entered in point 1.9. If
the
connection is successfully then the MS-SQL username, MS-SQL password
and the
MS-SQL servername are proper. If it is unsuccessful then check then
check the
username, password and the server name.
1.12 . After creating the system DSN, click OK to exit the ODBC Data Source
Administrator.
Note :- Now Please keep in mind the SystemDSN name you gave for the
source
MS-SQL Server. That was the name in the 6th point.
________________________________________
FILE. :-2. ENTRIES TO THE TNSNAMES.ORA
Here it is considered as the name of the HSMSQL as the systemDSN name You
created through odbc.
2.1
HSMSQL=
(DESCRIPTION=
(ADDRESS= (PROTOCOL=tcp)
(HOST=oracle server IP)
(PORT=1521)
)
(CONNECT_DATA =
(SERVICE_NAME=HSMSQL) ->
Needs to match with the
sid in the
listener.ora
)
HS clause goes in the description(HS = OK)
)
2.2 Here the HSMSQL is the name of the systemDSN created to connect to the
MS-SQL-SERVER through the odbc datasource administrator. The IP is the
IP of the
Oracle server where the oracle database is installed or through which
your are trying
to connect the ms-sql server database.
2.3 Save and Exit.
________________________________________
FILE. :- Here it is considered as the name of3. ENTRIES TO THE LISTENER.ORA
the HSMSQL as the systemDSN name You created through odbc.
3.1 (SID_DESC =
Needs to match the sid in tnsnames.ora(SID_NAME=HSMSQL)
(ORACLE_HOME=D:\oracle\product\10.1.0\Db_3)
hsodbc is the executable(PROGRAM =hsodbc)
)
3.2 Save and Exit.
________________________________________
4. STARTING THE LISTENER :-
Reload the Listener, and confirm that the HSODBC service is running.
4.1 After reloading the listener the below thing should be show, now here
the hsmsql is the systemdsn name is assumed in the listener.ora file
For example :
DOS> lsnrctl reload
LSNRCTL for 32-bit Windows: Version 10.1.0.2.0 - Production on
26-
AUG-2004 10:04:03
Copyright (c) 1991, 2004, Oracle. All rights reserved.
Connecting to
(DESCRIPTION= (ADDRESS= (PROTOCOL=IPC) (KEY=EXTPROC)))
The command completed successfully.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - -
DOS> lsnrctl services
LSNRCTL for 32-bit Windows: Version 9.2.0.4.0 - Production on 01-
JUL-2004 12:00:00
Copyright (c) 1991, 2002, Oracle Corporation. All rights
reserved.
Connecting to (DESCRIPTION= (ADDRESS= (PROTOCOL=IPC)
(KEY=EXTPROC0)))
Services Summary...
Service "HSMSQL" has 1 instance(s).
Instance "HSMSQL", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established: 1 refused: 0
LOCAL SERVER
Service "ORCL" has 1 instance(s).
Instance "ORCL", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established: 0 refused: 0 state: ready
LOCAL SERVER
The command completed successfully
4.2 Now in the 4.1 the red coloured HSMSQL service is shown as running,
that means the service is up to listen the queries.
5. CREATING THE INITIALIZATION FILE :-
The following procedure enables you to create the Initializing the service
by creating and customizing an initialization file for your Generic
Connectivity
agent.
5.1. Oracle Corporation supplies sample initialization files, inithsodbc.ora
for ODBC agents. The sample files are stored in the
\ORACLE_HOME\hs\admin
directory.
5.2 To create an initialization file for an ODBC, copy the applicable sample
initialization file from \ORACLE_HOME\hs\admin and rename the file to
name
initHS_SID.ora, where HS_SID is the system identifier you want to use
for the
instance of the non-Oracle system to which the agent connects.
(Please refer to
the point 1.6 name will SID that is if the name was msql here it
would be
HSMSQL. The suffix HS will be added to name of the systemdsn name.
Note: - The HS_SID is also used to identify how to connect to the
agent when you
Configure the listener by modifying the listener.ora file.
5.3 The HS_SID you add to the listener.ora file must match the HS_SID in an
initHS_SID.ora file, because the agent spawned by the listener
searches for a
matching initHS_SID.ora file. That is how each agent process gets its
initialization
information.
5.4 When you copy and rename your initHS_SID.ora file, ensure it remains in the
\ORACLE_HOME\hs\admin directory.
5.5 Then open the file HS_SID.ora file make the below changes.
odbc_data_source_nameHS_FDS_CONNECT_INFO = HSDSNNAME
HS_FDS_TRACE_LEVEL = OFF
Example: - If the name of the systemdsn was hsmsql then here it
will be:
HS_FDS_CONNECT_INFO = HSMSQL
HS_FDS_TRACE_LEVEL = OFF
Then save the file and exit.
===========================================================
6. CREATING THE DATABASE LINK TO ACCESS THE TARGET DATABASE :-
Now create the database link, here it is assumed that the name of the
systemDSN is
Hsmsql.
6.1
sql> create database link hsmsql
2. connect to “ms-sql user login” identified by
“ms-sql passwd”
3. using ‘hsmsql’;
Database link created
6.2 To test, run a simple query of a known table on the target
datastore.
Note :- But before executing this, the table employee should be
created first in
the MS-SQL server.
SQL> select * from employee_at_hsmsql;
EmpoyeeID EmployeeName
----------
--------------------------------------------------
1 Ralph
2 Sam
3 Monica
THIS MEANS THAT NOW YOU ARE ABLE TO QUERY THE REMOTE MS-SQL
DATABASE.
Note :- If any errors please refer to the APPENDIX B for
the common errors.
________________________________________
7. RESTRICTIONS ON OPERATIONS TO BE CARRIED ON THE REMOTE DATABASE FROM ORACLE.
On the remote database the DDL (Data Definition Language) statement cannot be
executed.
7.1 Creating the table on the remote database is not possible on a remote
database.
Example :
SQL> create table rama_at_hsmsql
2 (
3 name varchar,
4 address varchar,
5 phone varchar);
create table rama_at_hsmsql
*
ERROR at line 1:
ORA-02021: DDL operations are not allowed on a remote
database
7.2 Dropping the existing table from remote database not possible.
Example:
SQL> drop table emp_at_hsmsql;
drop table emp_at_hsmsql
*
ERROR at line 1:
ORA-02021: DDL operations are not allowed on a remote database
7.3 Selective queries are not possible on the remote database.
Example :
SQL> select * from employee_at_hsmsql
2 where EmpoyeeID='Ralph';
where EmpoyeeID='Ralph'
*
ERROR at line 2:
ORA-00904: "EMPOYEEID": invalid identifier
7.4 Deletion of the selective rows not possible on the remote
database.
Example:
SQL> delete from employee_at_hsmsql
2 where employeeid=4
3 ;
where employeeid=4
*
ERROR at line 2:
ORA-00904: "EMPLOYEEID": invalid identifier
7.5 Updation of the selective rows not possible. SQL> update employee_at_hsmsql
2 set employeeid=100
3 where employeeid=1;
where employeeid=1
*
ERROR at line 3:
ORA-00904: "EMPLOYEEID": invalid identifier
________________________________________
8. OPERATIONS THAT CAN BE CARRIED OUT ON THE REMOTE DATABASE FROM ORACLE. 8.1
Inserting the new records into the existing table. Example:-
SQL> desc emp_at_hsmsql;
Name
Null? Type
----------------------------------------- --------
----------------------------
empno
VARCHAR2(1)
ename
CHAR(1)
SQL> select * from emp_at_hsmsql;
e e
- -
1 j
SQL> insert into emp_at_hsmsql
2 values ('2','P');
1 row created.
SQL> select * from emp_at_hsmsql;
e e
- -
1 j
2 P
SQL> insert into employee_at_HSMSQL values(4,'Ramakrishna');
1 row created.
8.2 Deletion of the all rows at once in the table is possible, even it can be
rollbacked.
SQL> delete from employee_at_hsmsql;
3 rows deleted.
SQL> SELECT * FROM EMPLOYEE_at_HSMSQL; no rows selected
SQL> rollback;
Rollback complete.
SQL> SELECT * FROM EMPLOYEE_at_HSMSQL; EmpoyeeID EmployeeName
---------- --------------------------------------------------
1 Ralph
2 Sam
3 Monica
3 rows selected.
===========================================================
8.3 Creating the tables in the oracle from the existing tables on the remote
database. That
is duplication of tables from MS-SQL to Oracle.
SQL> select * from employee_at_hsmsql;
EmpoyeeID EmployeeName
---------- --------------------------------------------------
1 Ralph
2 Sam
3 Monica
3 rows selected.
SQL> create table employee as select * from employee_at_hsmsql;
Table created.
SQL> select * from employee;
EmpoyeeID EmployeeName
---------- --------------------------------------------------
1 Ralph
2 Sam
3 Monica
3 rows selected.
________________________________________
APPENDIX A
(Tables in the MS-SQL server)
A.1 Tables with data created in the MS-SQL Server.
Example:-
SQL> create table employee (
EmpoyeeID NUMBER(10),
EmployeeName VARCHAR2(50)
);
SQL> insert into employee values(1, 'Ralph');
SQL> insert into employee values(1, 'Sam');
SQL> insert into employee values(1, 'Monica');
• - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
• - - -
SQL> create table emp (
Empno VARCHAR2(1),
Ename CHAR(1)
);
SQL> insert into emp values('1', 'j');
SQL> insert into emp values('2', 'P');
SQL> insert into emp values('2', 'P');
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Clara
Devi
Sent: Thursday, August 04, 2005 4:34 PM
To: [email protected]
Subject: Re: [indo-oracle] ODBC
Sorry saya nanya lagi TG4MSQL itu bawaan oracle atau berdiri sendiri
soalnya saya cari di www.oracle.com ga nemu, jadi kalau pisah dari oracle
harus cari lagi cd nya
Thanks
> dear clara devi,
>
> untuk bisa connect dari oracle ke sql server, kamu harus intall TG4MSQL
> (Transparent Gateway for MS SQL Server) dulu, kalo kamu engga punya cd
> installationya, kamu bisa download di oracle.com, ini saya kirim juga
> petunjuk cara installnya dan cara connect ke sql servernya.
>
>
============================================================================
> =================
> PURPOSE
> -------
>
> This article provides a step-by-step guide setting up and
troubleshooting
>
> TG4MSQL (Transparent Gateway for MS SQL Server) for a Windows based
>
> platform. This note applies to TG4MSQL release 8.1.6.0.0 and 9.0.1.0.1 -
>
> both TG4MSQL versions use the MS SQL Server client library - as well to
>
> release 9.2.0.1.1 which uses ODBC as connect method.
>
>
>
> SCOPE & APPLICATION
>
> -------------------
>
> This bulletin is a summary of the manual.
>
>
>
> How to setup TG4MSQL
>
> --------------------
>
>
>
> 1)
>
> -For Oracle TG4MSQL V9.0.1 or 9.2:
>
> With the OUI (Oracle Universal Installer) install
>
> TG4MSQL. This product is part of the server
>
> installation CDs.
>
> ( Start OUI, choose a sep. Oracle_Home, select the Oracle
>
> database for installation. Then choose custom install. A
>
> product list pops up where you have to scroll down to
>
> ORACLE TRANSPARENT GATEWAY; click on the '+' in front and
>
> a product list opens. Choose the gateways you want to install)
>
>
>
> -For Oracle TG4MSQL V816:
>
> There is a separate CD containing Oracle Transparent Gateway
>
> for MS SQL Server release 8.1.6. Insert this CD and install TG4MSQL
>
> according to the screen messages.
>
>
>
> -BOTH:
>
> A directory called TG4MSQL will be created and a file called
>
> TG4MSQL.EXE is placed in the bin directory of the appropriate
>
> Oracle_Home.
>
>
>
>
>
> 2) TG4MSQL needs data dictionary tables in the Oracle database.
>
> To check their existence, run a query on
>
> i.e. SYS.HS_FDS_CLASS.
>
> If it fails, run the caths.sql script located in
ORACLE_HOME\RDBMS\ADMIN\
>
> as user sys or internal.
>
>
>
> 3) Make sure for gateway version 8.1.6 (8i) and 9.0.1.0.0 (9iR1) that
the
>
> Microsoft client is installed on the gateway machine (at least it is
>
> sufficient that the MS SQL Server Client DLL (ntwdblib.dll ) is
available
>
> in the search path.
>
> Perhaps copy the file into the bin directory of your Oracle_Home
>
> installation.
>
>
>
> For V9.2.0.1.2 (9iR2) gateways, the access method changed from the
client
>
> library to ODBC. So please make sure to have the MS SQL Server ODBC
>
> driver installed on the gateway machine. If it is not available,
download
>
> the latest MDAC Microsoft Data Access Components) from the Microsoft
Web
>
> page and install it. This package contains a SQL Server ODBC driver.
>
>
>
>
>
> 4) Tnsnames.ora.
>
> This file is in ORACLE_HOME\NETWORK\ADMIN.
>
> Add the following lines to the file:
>
>
>
> tg4msql.de.oracle.com = |<- adjust default domain depending
on
>
> the sqlnet.ora settings
>
> (DESCRIPTION=
>
> (ADDRESS=(PROTOCOL=tcp)
>
> (HOST=<HOSTNAME>) |<- adjust hostname
>
> (PORT=1521)) |<- adjust port
>
> (CONNECT_DATA=(SID=tg4msql))
>
> (HS=OK) |<- attention: HS is outside
> CONNECT_DATA
>
> )
>
>
>
>
>
> Note, a sample file is located in ORACLE_HOME\tg4msql\ADMIN.
>
>
>
> COMMON ERRORS:
>
> Make sure, that there are 2 closing brackets after the SID; the
>
> HS keyword is outside of the Connect Data block.
>
> Further make sure that only the TNS Alias is at the first position of
the
>
> line; all other lines must start at least with one SPACE (blank);
>
> otherwise it is identified as an alias and the configuration is not
> correct.
>
>
>
> 5) Listener.ora:
>
> This file is in ORACLE_HOME\NETWORK\ADMIN as well.
>
> Add the following line to the SID_List of the listener.ora and
restart
> the
>
> listener afterwards. ( After the restart a service handler for
tg4msql
>
> should exist).
>
>
>
> (SID_DESC=
>
> (SID_NAME=tg4msql)
>
> (ORACLE_HOME=e:\ora92) |<- adjust Oracle_Home directory
>
> (PROGRAM=tg4msql)
>
> )
>
>
>
> Note, a sample file is located in ORACLE_HOME\tg4msql\ADMIN.
>
>
>
> COMMON ERRORS:
>
> After configuring the listener, restart it from the command line
>
> (lsnrctl -> stop, start) and check the service summary. It must
contain
>
> 1 service handler for the TG4MSQL SID.
>
>
>
> 6) Adjust the configuration file of the gateway. It is located in
>
> ORACLE_HOME\TG4MSQL\ADMIN. The name depends on the SID you use for
the
>
> gateway.
>
> In our sample the listener SID is tg4msql and so the configuration
file
>
> must be named inittg4msql.ora.
>
>
>
> # This is a sample agent init file that contains the HS parameters
that
> are
>
> # needed for an ODBC Agent.
>
> #
>
> # HS init parameters
>
> #
>
> HS_FDS_CONNECT_INFO = <servername>.<database> |<- Please specify the
> server
>
> hostname and do
not
> use
>
> IP addresses.
>
> The dot is the
> delimeter
>
> and we use it to
> separate
>
> the servername
from
> the
>
> database name.
>
> HS_FDS_TRACE_LEVEL = 0 |<- trace levels are from off to
debug
>
>
>
>
>
> REMARK: Usually the following key is used to verify the connect options
>
> to the MS SQL Server:
>
> HKEY_LOCAL_MACHINE\
>
> SOFTWARE\
>
> Microsoft\
>
> MSSQLServer\
>
> Client\
>
>
ConnectTo
>
> This information normally specifies the ALIAS, the real server name,
> instances
>
> (if they are available) and port numbers of the SQL Server.
>
> Further details can be found in [NOTE:231997.1] TG4MSQL and MS SQL
>
> Server Instances.
>
>
>
>
>
> 7) Testing the connectivity between Oracle database and the SQL Server:
>
> - create a database link within the Oracle database to the SQL
Server:
>
> create database link tg4msql connect to "sa"
>
> identified by "<password of sa>" using 'tg4msql';
>
> - select * from [EMAIL PROTECTED];
>
>
>
> Example selecting a demo table of the MS Northwind database:
>
> select "TerritoryID" from "EmployeeTerritories"@<link name>;
>
>
>
> COMMON ERRORS:
>
> The usernames, passwords, table names, views, columns ... are case
> sensitive.
>
> For creating the database link, make sure you surround the username,
> password
>
> by double quotes and write them as they are defined in the MS SQL
Server.
>
>
>
> Another common error is, that the TG4MSQL does not allow OS
> Authentication
>
> (Windows Authentication) for the SQL Server. Only SQL Server
> authentication
>
> with a username AND a password is supported. Make sure, that the SQL
> Server
>
> Security option is checked to allow both authentication methods.
>
>
>
>
>
> 8) Useful SQLServer commands.
>
> sp_help - gives help on all the commands
>
> sp_addlogin - sets up a login user account
>
> sp_adduser - sets up a userid to use an individual database
>
> use {database} - changes the database which sql is being targetted
> against.
>
> sp_droplogin - remove a user account
>
> sp_dropuser - remove a user from a database.
>
>
>
>
>
>
>
>
>
>
############################################################################
> #######
>
>
>
> COMMON ERRORS and SOLUTIONS
>
>
>
>
############################################################################
> #######
>
>
>
> /********************************************************************/
>
> ORA-28509: unable to establish a connection to non-Oracle system
>
> ORA-02063: preceding line from TG4MSQL
>
> /********************************************************************/
>
> cause:
>
> This indicates a problem with the Oracle configuration files.
>
> Action:
>
> Make sure the HOST parameter in the tnsnames.ora file is correct.
>
> Make sure the PORT number is correct.
>
> Make sure the SID name is correct in both the TNSNAMES.ORA and
> LISTENER.ORA
>
>
>
> /********************************************************************/
>
> ORA-28500: connection from ORACLE to a non-Oracle system returned this
> message:
>
> [Transparent gateway for MS SQL Server] The environment variable
>
> <HS_FDS_CONNECT_INFO> is not set.
>
> ORA-02063: preceding 2 lines from TG4MSQL
>
> /********************************************************************/
>
> cause:
>
> Incorrect parameter settings in the HS init.ora file.
>
> Action:
>
> Check HS_FDS_CONNECT_INFO in the TG4MSQL init.ora file.
>
> It might be missing or TG4MSQL is not able to find the correct
>
> initialisation file.
>
> Make sure the HS init.ora file exists in the
ORACLE_HOME\tg4msql\admin
>
> directory and has the same name as the SID in the LISTENER.ORA.
>
> Example: If SID=mssql in the listener.ora file, then the nit.ora
file
>
> would be named ORACLE_HOME\hs\admin\initmssql.ora
>
>
>
> /********************************************************************/
>
> ORA-00942: table or view does not exist
>
> [Transparent gateway for ODBC]DRV_OpenTable: [Mircosoft ][ODBC SQL
Server
>
> Driver][SQL Server]Invalid object name '%table%'. (SQL State: S0002; SQL
> Code:
>
> 208)
>
> ORA-02063: preceding 2 lines from TG4MSQL
>
> /********************************************************************/
>
> cause:
>
> The init.ora file speciffies the wrong MS SQL Server database.
>
> A second cause could be, that MS SQL Server tables are case
sensitive
>
> and thus should be surrounded by double quotes.
>
>
============================================================================
> ========================
>
> smoga membantu
>
> salam,
>
> Irawan
>
>
>
>
>
> ----- Original Message -----
> From: "Clara Devi" <[EMAIL PROTECTED]>
> To: <[email protected]>
> Sent: Thursday, August 04, 2005 2:26 PM
> Subject: [indo-oracle] ODBC
>
>
> > ALlow saya mohon bantuannya donk da pusing nih :)
> > Saya mau connect dari oracle 8.0.5 ke SQL Server 2000, saya coba
gunakan
> ODBC.
> > di System DNS saya add berdasarkan SQL server dan step-step saya
sudah
> ikuti semua sampai Test Data Source .. Tests Completed successfully.
> >
> > Lalu langkah selanjutnya di orcle gimana ya.. pls tolong masukkannya
donk
> >
> >
> > Thanks B4
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> >
> > --
> > -----------I.N.D.O - O.R.A.C.L.E---------------
> > Keluar: [EMAIL PROTECTED]
> > Website: http://indo-oracle.lizt.org (NEW)
> > -----------------------------------------------
> >
> > Bergabung dengan Indonesia Thin Client User Groups,
> > Terminal Server, Citrix, New Moon Caneveral, di:
> > http://indo-thin.vze.com
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
> The contents of this e-mail may be confidential and the unauthorized
use,
> copying, or dissemination of it and any attachments to it, is
prohibited.
> Internet communications are not secure and Dexa Group companies do not,
> therefore, accept legal responsibility for the contents of this message
nor
> for any damage caused by viruses. The views expressed here do not
necessarily
> represent those of Dexa Group companies.
>
>
>
>
>
> --
> -----------I.N.D.O - O.R.A.C.L.E---------------
> Keluar: [EMAIL PROTECTED]
> Website: http://indo-oracle.lizt.org (NEW)
> -----------------------------------------------
>
> Bergabung dengan Indonesia Thin Client User Groups,
> Terminal Server, Citrix, New Moon Caneveral, di:
> http://indo-thin.vze.com
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
--
-----------I.N.D.O - O.R.A.C.L.E---------------
Keluar: [EMAIL PROTECTED]
Website: http://indo-oracle.lizt.org (NEW)
-----------------------------------------------
Bergabung dengan Indonesia Thin Client User Groups,
Terminal Server, Citrix, New Moon Caneveral, di:
http://indo-thin.vze.com
Yahoo! Groups Links
------------------------ Yahoo! Groups Sponsor --------------------~-->
<font face=arial size=-1><a
href="http://us.ard.yahoo.com/SIG=12hl7mp0a/M=362131.6882499.7825260.1510227/D=groups/S=1705007183:TM/Y=YAHOO/EXP=1123213641/A=2889191/R=0/SIG=10r90krvo/*http://www.thebeehive.org
">Get Bzzzy! (real tools to help you find a job) Welcome to the Sweet Life
-�brought to you by One Economy</a>.</font>
--------------------------------------------------------------------~->
--
-----------I.N.D.O - O.R.A.C.L.E---------------
Keluar: [EMAIL PROTECTED]
Website: http://indo-oracle.lizt.org (NEW)
-----------------------------------------------
Bergabung dengan Indonesia Thin Client User Groups,
Terminal Server, Citrix, New Moon Caneveral, di:
http://indo-thin.vze.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/indo-oracle/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
