Oracle Woes

Cathy Taddei

Oracle Woes
We are unfortunately running the Oracle Transparent Gateway to access
mainframe DB2 from Windows. Users sign on to an Oracle instance on the
mainframe (Oracle7 Server Release 7.3.3.6.2), and from there access the
gateway to DB2. We are finally upgrading to z/OS 1.4, from OS/390 2.10.
When I start Oracle under z/OS, I'm getting messages like this:

SVRMGR> ALTER DATABASE ORAD MOUNT;
Unable to initialize Media Manager interface for CONTROL2.
ORA-04217, FUNC=MMINIT, RS=0408400C
Unable to initialize Media Manager interface for CONTROL1.
ORA-04217, FUNC=MMINIT, RS=0408400C
Statement processed.
SVRMGR> ALTER DATABASE OPEN;
Unable to initialize Media Manager interface for DB1 .
ORA-04217, FUNC=MMINIT, RS=0408400C
Unable to initialize Media Manager interface for DB2 .
ORA-04217, FUNC=MMINIT, RS=0408400C

Has anyone else encountered anything like this? Is there a remedy?

Unfortunately, I cannot yet test the gateway itself. Is anyone else
running OTG Release 4.0.1.1.0 under z/OS?

Thanks,
Cathy Taddei

------------------------------------------------------------------------------

This email is confidential and may be legally privileged.

It is intended solely for the addressee. Access to this email by anyone else, unless expressly approved by the sender or an authorized addressee, is unauthorized.

If you are not the intended recipient, any disclosure, copying, distribution or any action omitted or taken in reliance on it, is prohibited and may be unlawful. If you believe that you have received this email in error, please contact the sender, delete this e-mail and destroy all copies.

======

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Jim Tonchick

Re: Oracle Woes
(in response to Cathy Taddei)
You should contact Oracle support to verify that the release that you are
running will support running on z/OS 1.4. You might need to apply maintenance to
Oracle7, or maybe even upgrade to a higher release.

When you call Oracle support give them the release of Oracle7 you are
running, any maintenance you have applied to Oracle, and the maintenance level of
z/OS 1.4 (such as RSU0403, PUT0403 or PDO0403). Also, give them the messages
being displayed when you attempt to bring up Oracle under z/OS. They should then
be able to tell you what you need to do.

Jim Tonchick

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Edward Long

Re: Oracle Woes
(in response to Jim Tonchick)
Oracle 7 is fully depreciated; I'm surprised it would work at all.
Current is Oracle 9I or 10g.
I'd not waste a lot of time on something that old.

"Taddei, Cathy" <[login to unmask email]> wrote:

We are unfortunately running the Oracle Transparent Gateway to access mainframe DB2 from Windows. Users sign on to an Oracle instance on the mainframe (Oracle7 Server Release 7.3.3.6.2), and from there access the gateway to DB2. We are finally upgrading to z/OS 1.4, from OS/390 2.10. When I start Oracle under z/OS, I'm getting messages like this:

SVRMGR> ALTER DATABASE ORAD MOUNT;
Unable to initialize Media Manager interface for CONTROL2.
ORA-04217, FUNC=MMINIT, RS=0408400C
Unable to initialize Media Manager interface for CONTROL1.
ORA-04217, FUNC=MMINIT, RS=0408400C
Statement processed.
SVRMGR> ALTER DATABASE OPEN;
Unable to initialize Media Manager interface for DB1 .
ORA-04217, FUNC=MMINIT, RS=0408400C
Unable to initialize Media Manager interface for DB2 .
ORA-04217, FUNC=MMINIT, RS=0408400C

Has anyone else encountered anything like this? Is there a remedy?

Unfortunately, I cannot yet test the gateway itself. Is anyone else running OTG Release 4.0.1.1.0 under z/OS?

Thanks,
Cathy Taddei

------------------------------------------------------------------------------

This email is confidential and may be legally privileged.

It is intended solely for the addressee. Access to this email by anyone else, unless expressly approved by the sender or an authorized addressee, is unauthorized.

If you are not the intended recipient, any disclosure, copying, distribution or any action omitted or taken in reliance on it, is prohibited and may be unlawful. If you believe that you have received this email in error, please contact the sender, delete this e-mail and destroy all copies.

=====

--------------------------------------------------------------------------------- Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Edward Long

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

DAVID PETERSEN

Re: Oracle Woes
(in response to Edward Long)
Cathy,

We are unlucky enough to have the same software. It will not start up
under zos 1.4. You must upgrade the software. We went through the
same experience about 16-18 months ago. The newer version is very
different than the version you are on.

Good luck.

Dave Petersen

Ed Long wrote:

> Oracle 7 is fully depreciated; I'm surprised it would work at all.
> Current is Oracle 9I or 10g.
> I'd not waste a lot of time on something that old.
>
> "Taddei, Cathy" <[login to unmask email]> wrote:
>
> We are unfortunately running the Oracle Transparent Gateway to
> access mainframe DB2 from Windows. Users sign on to an Oracle
> instance on the mainframe (Oracle7 Server Release 7.3.3.6.2), and
> from there access the gateway to DB2. We are finally upgrading to
> z/OS 1.4, from OS/390 2.10. When I start Oracle under z/OS, I'm
> getting messages like this:
>
> SVRMGR> ALTER DATABASE ORAD MOUNT;
> Unable to initialize Media Manager interface for CONTROL2.
> ORA-04217, FUNC=MMINIT, RS=0408400C
> Unable to initialize Media Manager interface for CONTROL1.
> ORA-04217, FUNC=MMINIT, RS=0408400C
> Statement processed.
> SVRMGR> ALTER DATABASE OPEN;
> Unable to initialize Media Manager interface for DB1 .
> ORA-04217, FUNC=MMINIT, RS=0408400C
> Unable to initialize Media Manager interface for DB2 .
> ORA-04217, FUN! C=MMINIT, RS=0408400C
>
> Has anyone else encountered anything like this? Is there a remedy?
>
> Unfortunately, I cannot yet test the gateway itself. Is anyone
> else running OTG Release 4.0.1.1.0 under z/OS?
>
> Thanks,
> Cathy Taddei
>
> ------------------------------------------------------------------------------
>
> This email is confidential and may be legally privileged.
>
> It is intended solely for the addressee. Access to this email by
> anyone else, unless expressly approved by the sender or an
> authorized addressee, is unauthorized.
>
> If you are not the intended recipient, any disclosure, copying,
> distribution or any action omitted or taken in reliance on it, is
> prohibited and may be unlawful. If you believe that you have
> received this email in error, please contact the sender, delete
> this e-mail and destroy all copies.
>
> ======
>
> ---------------------------------------------------------------------------------
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives
> and home page at http://www.idugdb2-l.org/archives/db2-l.html.
> From that page select "Join or Leave the list". The IDUG DB2-L FAQ
> is! at http://www.idugdb2-l.org. The IDUG List Admins can be
> reached at [login to unmask email] Find out the latest on
> IDUG conferences at http://conferences.idug.org/index.cfm
>
>
>
> Edward Long
> ---------------------------------------------------------------------------------
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
> home page at http://www.idugdb2-l.org/archives/db2-l.html. From that
> page select "Join or Leave the list". The IDUG DB2-L FAQ is at
> http://www.idugdb2-l.org. The IDUG List Admins can be reached at
> [login to unmask email] Find out the latest on IDUG
> conferences at http://conferences.idug.org/index.cfm



---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Sam Kitty

Re: Oracle Woes
(in response to DAVID PETERSEN)
It is a bug. This is what is on Metalink:
Bug 2394208
<http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_
id=2394208&p_database_id=BUG> identifies that a change in IBM Media
Manager in z/OS 1.3 and later


causes Oracle Database Open failure. Oracle code has been changed to
accomodate this.


However, older versions that are no longer supported will not be
corrected.


Thus if you are planning to upgrade to z/OS 1.3 or 1.4, you should
ensure you


are running a version of Oracle that is eligible for corrective
maintenance.




Versions Affected


~~~~~~~~~~~~~~~~~


7.3, 8.0, 8.1.7.



Platforms Affected


~~~~~~~~~~~~~~~~~~


IBM z/OS Versions 1.3, 1.4.





Description


~~~~~~~~~~~



Database startup fails to open control file due to z/OS Media Manager
interface failure.


changes introduced with z/OS 1.3.



Likelihood of Occurrence


~~~~~~~~~~~~~~~~~~~~~~~~


Any "MPM"-based implementation of Oracle for z/OS (OS/390)



Possible Symptoms


~~~~~~~~~~~~~~~~~


Error messages on SYSLOG:



Unable to initialize Media Manager interface for <control_file_datafile>



ORA-04217, FUNC=MMINIT, RS=0408400C


Ivan Krnic

DBA




-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]On
Behalf Of Taddei, Cathy
Sent: Wednesday, December 15, 2004 3:46 PM
To: [login to unmask email]
Subject: Oracle Woes



We are unfortunately running the Oracle Transparent Gateway to access
mainframe DB2 from Windows. Users sign on to an Oracle instance on the
mainframe (Oracle7 Server Release 7.3.3.6.2), and from there access the
gateway to DB2. We are finally upgrading to z/OS 1.4, from OS/390 2.10.
When I start Oracle under z/OS, I'm getting messages like this:

SVRMGR> ALTER DATABASE ORAD MOUNT;
Unable to initialize Media Manager interface for CONTROL2.
ORA-04217, FUNC=MMINIT, RS=0408400C
Unable to initialize Media Manager interface for CONTROL1.
ORA-04217, FUNC=MMINIT, RS=0408400C
Statement processed.
SVRMGR> ALTER DATABASE OPEN;
Unable to initialize Media Manager interface for DB1 .
ORA-04217, FUNC=MMINIT, RS=0408400C
Unable to initialize Media Manager interface for DB2 .
ORA-04217, FUNC=MMINIT, RS=0408400C

Has anyone else encountered anything like this? Is there a remedy?

Unfortunately, I cannot yet test the gateway itself. Is anyone else
running OTG Release 4.0.1.1.0 under z/OS?

Thanks,
Cathy Taddei

------------------------------------------------------------------------
------

This email is confidential and may be legally privileged.

It is intended solely for the addressee. Access to this email by anyone
else, unless expressly approved by the sender or an authorized
addressee, is unauthorized.

If you are not the intended recipient, any disclosure, copying,
distribution or any action omitted or taken in reliance on it, is
prohibited and may be unlawful. If you believe that you have received
this email in error, please contact the sender, delete this e-mail and
destroy all copies.


======


------------------------------------------------------------------------
--------- Welcome to the IDUG DB2-L list. To unsubscribe, go to the
archives and home page at http://www.idugdb2-l.org/archives/db2-l.html.
From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm


---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Cathy Taddei

Re: Oracle Woes
(in response to Sam Kitty)
Thank you all for your great research and comments! I was getting
pressure from above to "fix it", but now that has changed to "replace
it". Yay!!!

FYI, I also tested to see if I could use an Oracle instance on another
platform to talk to the gateway on the mainframe, but the gateway still
depends on SQLNET, which is an Oracle 7 client, and Oracle 9.2. WILL NOT
talk to Oracle 7. So for this shop, the Oracle Transparent Gateway is
"morally, ethically, spiritually, physically, positively, absolutely,
undeniably and reliably Dead!!" (quote from the Wizard of OZ)

Now, the search is on for the world's absolutely cheapest ODBC driver...

Regards,
Cathy Taddei

________________________________

From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Krnic, Ivan B.
Sent: Thursday, December 16, 2004 6:05 AM
To: [login to unmask email]
Subject: Re: Oracle Woes


It is a bug. This is what is on Metalink:
Bug 2394208
<http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_
id=2394208&p_database_id=BUG> identifies that a change in IBM Media
Manager in z/OS 1.3 and later

causes Oracle Database Open failure. Oracle code has been changed to
accomodate this.

However, older versions that are no longer supported will not be
corrected.

Thus if you are planning to upgrade to z/OS 1.3 or 1.4, you should
ensure you

are running a version of Oracle that is eligible for corrective
maintenance.

Versions Affected

~~~~~~~~~~~~~~~~~

7.3, 8.0, 8.1.7.

Platforms Affected

~~~~~~~~~~~~~~~~~~

IBM z/OS Versions 1.3, 1.4.



Description

~~~~~~~~~~~

Database startup fails to open control file due to z/OS Media Manager
interface failure.

changes introduced with z/OS 1.3.

Likelihood of Occurrence

~~~~~~~~~~~~~~~~~~~~~~~~

Any "MPM"-based implementation of Oracle for z/OS (OS/390)

Possible Symptoms

~~~~~~~~~~~~~~~~~

Error messages on SYSLOG:

Unable to initialize Media Manager interface for <control_file_datafile>


ORA-04217, FUNC=MMINIT, RS=0408400C


Ivan Krnic

DBA




-----Original Message-----
From: DB2 Data Base Discussion List
[mailto:[login to unmask email]On Behalf Of Taddei, Cathy
Sent: Wednesday, December 15, 2004 3:46 PM
To: [login to unmask email]
Subject: Oracle Woes



We are unfortunately running the Oracle Transparent Gateway to
access mainframe DB2 from Windows. Users sign on to an Oracle instance
on the mainframe (Oracle7 Server Release 7.3.3.6.2), and from there
access the gateway to DB2. We are finally upgrading to z/OS 1.4, from
OS/390 2.10. When I start Oracle under z/OS, I'm getting messages like
this:

SVRMGR> ALTER DATABASE ORAD MOUNT;
Unable to initialize Media Manager interface for CONTROL2.
ORA-04217, FUNC=MMINIT, RS=0408400C
Unable to initialize Media Manager interface for CONTROL1.
ORA-04217, FUNC=MMINIT, RS=0408400C
Statement processed.
SVRMGR> ALTER DATABASE OPEN;
Unable to initialize Media Manager interface for DB1 .
ORA-04217, FUNC=MMINIT, RS=0408400C
Unable to initialize Media Manager interface for DB2 .
ORA-04217, FUNC=MMINIT, RS=0408400C

Has anyone else encountered anything like this? Is there a
remedy?

Unfortunately, I cannot yet test the gateway itself. Is anyone
else running OTG Release 4.0.1.1.0 under z/OS?

Thanks,
Cathy Taddei




------------------------------------------------------------------------------

This email is confidential and may be legally privileged.

It is intended solely for the addressee. Access to this email by anyone else, unless expressly approved by the sender or an authorized addressee, is unauthorized.

If you are not the intended recipient, any disclosure, copying, distribution or any action omitted or taken in reliance on it, is prohibited and may be unlawful. If you believe that you have received this email in error, please contact the sender, delete this e-mail and destroy all copies.

======

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Myron Miller

Re: Oracle Woes
(in response to Cathy Taddei)
We run from Oracle 9.2 on AIX to the mainframe using Oracle gateway for some
things. I don't like it as it performs really poorly. But it works pretty
well.

What we do is go directly from the AIX box thru the gateway to DB2. We don't
have Oracle on the mainframe at all. So it's a direct link from the AIX Oracle
to gateway to DB2 not going thru anything else.

So I don't understand you issue with Oracle 7 SQLNET. We use whatever SQLNET
that is on the client's machine that is used to connect to the Oracle 9
platform.

I will grant that almost any ODBC direct driver will outperform the Oracle
Gateway. We converted several app's from the gateway to direct DB2 Connect
calls. The apps went from average 4 sec response time per call to subsecond
avg. Fairly significant improvement in response times.

Myron
--- "Taddei, Cathy" <[login to unmask email]> wrote:

> Thank you all for your great research and comments! I was getting
> pressure from above to "fix it", but now that has changed to "replace
> it". Yay!!!
>
> FYI, I also tested to see if I could use an Oracle instance on another
> platform to talk to the gateway on the mainframe, but the gateway still
> depends on SQLNET, which is an Oracle 7 client, and Oracle 9.2. WILL NOT
> talk to Oracle 7. So for this shop, the Oracle Transparent Gateway is
> "morally, ethically, spiritually, physically, positively, absolutely,
> undeniably and reliably Dead!!" (quote from the Wizard of OZ)
>
> Now, the search is on for the world's absolutely cheapest ODBC driver...
>
> Regards,
> Cathy Taddei
>
> ________________________________
>
> From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
> Behalf Of Krnic, Ivan B.
> Sent: Thursday, December 16, 2004 6:05 AM
> To: [login to unmask email]
> Subject: Re: Oracle Woes
>
>
> It is a bug. This is what is on Metalink:
> Bug 2394208
> <http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_
> id=2394208&p_database_id=BUG> identifies that a change in IBM Media
> Manager in z/OS 1.3 and later
>
> causes Oracle Database Open failure. Oracle code has been changed to
> accomodate this.
>
> However, older versions that are no longer supported will not be
> corrected.
>
> Thus if you are planning to upgrade to z/OS 1.3 or 1.4, you should
> ensure you
>
> are running a version of Oracle that is eligible for corrective
> maintenance.
>
> Versions Affected
>
> ~~~~~~~~~~~~~~~~~
>
> 7.3, 8.0, 8.1.7.
>
> Platforms Affected
>
> ~~~~~~~~~~~~~~~~~~
>
> IBM z/OS Versions 1.3, 1.4.
>
>
>
> Description
>
> ~~~~~~~~~~~
>
> Database startup fails to open control file due to z/OS Media Manager
> interface failure.
>
> changes introduced with z/OS 1.3.
>
> Likelihood of Occurrence
>
> ~~~~~~~~~~~~~~~~~~~~~~~~
>
> Any "MPM"-based implementation of Oracle for z/OS (OS/390)
>
> Possible Symptoms
>
> ~~~~~~~~~~~~~~~~~
>
> Error messages on SYSLOG:
>
> Unable to initialize Media Manager interface for <control_file_datafile>
>
>
> ORA-04217, FUNC=MMINIT, RS=0408400C
>
>
> Ivan Krnic
>
> DBA
>
>
>
>
> -----Original Message-----
> From: DB2 Data Base Discussion List
> [mailto:[login to unmask email]On Behalf Of Taddei, Cathy
> Sent: Wednesday, December 15, 2004 3:46 PM
> To: [login to unmask email]
> Subject: Oracle Woes
>
>
>
> We are unfortunately running the Oracle Transparent Gateway to
> access mainframe DB2 from Windows. Users sign on to an Oracle instance
> on the mainframe (Oracle7 Server Release 7.3.3.6.2), and from there
> access the gateway to DB2. We are finally upgrading to z/OS 1.4, from
> OS/390 2.10. When I start Oracle under z/OS, I'm getting messages like
> this:
>
> SVRMGR> ALTER DATABASE ORAD MOUNT;
> Unable to initialize Media Manager interface for CONTROL2.
> ORA-04217, FUNC=MMINIT, RS=0408400C
> Unable to initialize Media Manager interface for CONTROL1.
> ORA-04217, FUNC=MMINIT, RS=0408400C
> Statement processed.
> SVRMGR> ALTER DATABASE OPEN;
> Unable to initialize Media Manager interface for DB1 .
> ORA-04217, FUNC=MMINIT, RS=0408400C
> Unable to initialize Media Manager interface for DB2 .
> ORA-04217, FUNC=MMINIT, RS=0408400C
>
> Has anyone else encountered anything like this? Is there a
> remedy?
>
> Unfortunately, I cannot yet test the gateway itself. Is anyone
> else running OTG Release 4.0.1.1.0 under z/OS?
>
> Thanks,
> Cathy Taddei
>
>
>
>
>
------------------------------------------------------------------------------
>
> This email is confidential and may be legally privileged.
>
> It is intended solely for the addressee. Access to this email by anyone else,
> unless expressly approved by the sender or an authorized addressee, is
> unauthorized.
>
> If you are not the intended recipient, any disclosure, copying, distribution
> or any action omitted or taken in reliance on it, is prohibited and may be
> unlawful. If you believe that you have received this email in error, please
> contact the sender, delete this e-mail and destroy all copies.
>
>
=====
>
>
---------------------------------------------------------------------------------
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
> page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
> "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org.
> The IDUG List Admins can be reached at [login to unmask email] Find
> out the latest on IDUG conferences at http://conferences.idug.org/index.cfm
>

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Cathy Taddei

Re: Oracle Woes
(in response to Myron Miller)
We have two tasks on the mainframe that comprise the gateway: SQLNET and
G4ssid. When we tried to access the gateway from Oracle 9.2 on Unix, we
got an error message saying it could not talk to an Oracle 7 system.
When I asked my Oracle guru how it knew my Oracle DB was version 7 when
we were not accessing it, he explained that the SQLNET task was an
Oracle client. I will admit that my understanding of this whole Oracle
gateway thing is rather vague. At this point, if there is any way to
make it work under z/OS, I'd rather remain ignorant of it, so I can
blissfully continue on my course to trash the thing. Wait, I didn't say
that out loud, did I?
:)
Regards,
Cathy Taddei

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Myron Miller
Sent: Thursday, December 16, 2004 2:19 PM
To: [login to unmask email]
Subject: Re: Oracle Woes

We run from Oracle 9.2 on AIX to the mainframe using Oracle gateway for
some
things. I don't like it as it performs really poorly. But it works
pretty
well.

What we do is go directly from the AIX box thru the gateway to DB2. We
don't
have Oracle on the mainframe at all. So it's a direct link from the AIX
Oracle
to gateway to DB2 not going thru anything else.

So I don't understand you issue with Oracle 7 SQLNET. We use whatever
SQLNET
that is on the client's machine that is used to connect to the Oracle 9
platform.

I will grant that almost any ODBC direct driver will outperform the
Oracle
Gateway. We converted several app's from the gateway to direct DB2
Connect
calls. The apps went from average 4 sec response time per call to
subsecond
avg. Fairly significant improvement in response times.

Myron
--- "Taddei, Cathy" <[login to unmask email]> wrote:

> Thank you all for your great research and comments! I was getting
> pressure from above to "fix it", but now that has changed to "replace
> it". Yay!!!
>
> FYI, I also tested to see if I could use an Oracle instance on another
> platform to talk to the gateway on the mainframe, but the gateway
still
> depends on SQLNET, which is an Oracle 7 client, and Oracle 9.2. WILL
NOT
> talk to Oracle 7. So for this shop, the Oracle Transparent Gateway is
> "morally, ethically, spiritually, physically, positively, absolutely,
> undeniably and reliably Dead!!" (quote from the Wizard of OZ)
>
> Now, the search is on for the world's absolutely cheapest ODBC
driver...
>
> Regards,
> Cathy Taddei
>
> ________________________________
>
> From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
> Behalf Of Krnic, Ivan B.
> Sent: Thursday, December 16, 2004 6:05 AM
> To: [login to unmask email]
> Subject: Re: Oracle Woes
>
>
> It is a bug. This is what is on Metalink:
> Bug 2394208
>
<http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_
> id=2394208&p_database_id=BUG> identifies that a change in IBM Media
> Manager in z/OS 1.3 and later
>
> causes Oracle Database Open failure. Oracle code has been changed to
> accomodate this.
>
> However, older versions that are no longer supported will not be
> corrected.
>
> Thus if you are planning to upgrade to z/OS 1.3 or 1.4, you should
> ensure you
>
> are running a version of Oracle that is eligible for corrective
> maintenance.
>
> Versions Affected
>
> ~~~~~~~~~~~~~~~~~
>
> 7.3, 8.0, 8.1.7.
>
> Platforms Affected
>
> ~~~~~~~~~~~~~~~~~~
>
> IBM z/OS Versions 1.3, 1.4.
>
>
>
> Description
>
> ~~~~~~~~~~~
>
> Database startup fails to open control file due to z/OS Media Manager
> interface failure.
>
> changes introduced with z/OS 1.3.
>
> Likelihood of Occurrence
>
> ~~~~~~~~~~~~~~~~~~~~~~~~
>
> Any "MPM"-based implementation of Oracle for z/OS (OS/390)
>
> Possible Symptoms
>
> ~~~~~~~~~~~~~~~~~
>
> Error messages on SYSLOG:
>
> Unable to initialize Media Manager interface for
<control_file_datafile>
>
>
> ORA-04217, FUNC=MMINIT, RS=0408400C
>
>
> Ivan Krnic
>
> DBA
>
>
>
>
> -----Original Message-----
> From: DB2 Data Base Discussion List
> [mailto:[login to unmask email]On Behalf Of Taddei, Cathy
> Sent: Wednesday, December 15, 2004 3:46 PM
> To: [login to unmask email]
> Subject: Oracle Woes
>
>
>
> We are unfortunately running the Oracle Transparent Gateway to
> access mainframe DB2 from Windows. Users sign on to an Oracle
instance
> on the mainframe (Oracle7 Server Release 7.3.3.6.2), and from there
> access the gateway to DB2. We are finally upgrading to z/OS 1.4, from
> OS/390 2.10. When I start Oracle under z/OS, I'm getting messages
like
> this:
>
> SVRMGR> ALTER DATABASE ORAD MOUNT;
> Unable to initialize Media Manager interface for CONTROL2.
> ORA-04217, FUNC=MMINIT, RS=0408400C
> Unable to initialize Media Manager interface for CONTROL1.
> ORA-04217, FUNC=MMINIT, RS=0408400C
> Statement processed.
> SVRMGR> ALTER DATABASE OPEN;
> Unable to initialize Media Manager interface for DB1 .
> ORA-04217, FUNC=MMINIT, RS=0408400C
> Unable to initialize Media Manager interface for DB2 .
> ORA-04217, FUNC=MMINIT, RS=0408400C
>
> Has anyone else encountered anything like this? Is there a
> remedy?
>
> Unfortunately, I cannot yet test the gateway itself. Is
anyone
> else running OTG Release 4.0.1.1.0 under z/OS?
>
> Thanks,
> Cathy Taddei
>
>
>
>
>
------------------------------------------------------------------------
------
>
> This email is confidential and may be legally privileged.
>
> It is intended solely for the addressee. Access to this email by
anyone else,
> unless expressly approved by the sender or an authorized addressee, is
> unauthorized.
>
> If you are not the intended recipient, any disclosure, copying,
distribution
> or any action omitted or taken in reliance on it, is prohibited and
may be
> unlawful. If you believe that you have received this email in error,
please
> contact the sender, delete this e-mail and destroy all copies.
>
>

======
>
>
------------------------------------------------------------------------
---------
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home
> page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select
> "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org.
> The IDUG List Admins can be reached at
[login to unmask email] Find
> out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm
>

------------------------------------------------------------------------
---------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that
page select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm


------------------------------------------------------------------------------

This email is confidential and may be legally privileged.

It is intended solely for the addressee. Access to this email by anyone else, unless expressly approved by the sender or an authorized addressee, is unauthorized.

If you are not the intended recipient, any disclosure, copying, distribution or any action omitted or taken in reliance on it, is prohibited and may be unlawful. If you believe that you have received this email in error, please contact the sender, delete this e-mail and destroy all copies.

======

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Joubert Gregory

Re: Oracle Woes
(in response to Cathy Taddei)
The components of the SQLNET has been similar over the versions, which
allowed for forward compatibility, Oracle 7.3 could talk to 8.0 & 8.1 (I had
not tried 7.3 to 9). Oracle (in its wisdom) decided to restrict access from
a 9.2 client to a number of out dated versions of databases (7.3, 8.0 & some
of the 8.1). I have found that 8.1.6 client is the best as it will allow
connections from 7.3 to 9.2 databases and I believe our Oracle DBA's may
have also connected through to 10g.

Use this as you need.

Gregory Joubert

-----Original Message-----
From: Taddei, Cathy [mailto:[login to unmask email]
Sent: Friday, 17 December 2004 10:05 AM
To: [login to unmask email]
Subject: Re: Oracle Woes

We have two tasks on the mainframe that comprise the gateway: SQLNET and
G4ssid. When we tried to access the gateway from Oracle 9.2 on Unix, we
got an error message saying it could not talk to an Oracle 7 system.
When I asked my Oracle guru how it knew my Oracle DB was version 7 when
we were not accessing it, he explained that the SQLNET task was an
Oracle client. I will admit that my understanding of this whole Oracle
gateway thing is rather vague. At this point, if there is any way to
make it work under z/OS, I'd rather remain ignorant of it, so I can
blissfully continue on my course to trash the thing. Wait, I didn't say
that out loud, did I?
:)
Regards,
Cathy Taddei

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Myron Miller
Sent: Thursday, December 16, 2004 2:19 PM
To: [login to unmask email]
Subject: Re: Oracle Woes

We run from Oracle 9.2 on AIX to the mainframe using Oracle gateway for
some
things. I don't like it as it performs really poorly. But it works
pretty
well.

What we do is go directly from the AIX box thru the gateway to DB2. We
don't
have Oracle on the mainframe at all. So it's a direct link from the AIX
Oracle
to gateway to DB2 not going thru anything else.

So I don't understand you issue with Oracle 7 SQLNET. We use whatever
SQLNET
that is on the client's machine that is used to connect to the Oracle 9
platform.

I will grant that almost any ODBC direct driver will outperform the
Oracle
Gateway. We converted several app's from the gateway to direct DB2
Connect
calls. The apps went from average 4 sec response time per call to
subsecond
avg. Fairly significant improvement in response times.

Myron
--- "Taddei, Cathy" <[login to unmask email]> wrote:

> Thank you all for your great research and comments! I was getting
> pressure from above to "fix it", but now that has changed to "replace
> it". Yay!!!
>
> FYI, I also tested to see if I could use an Oracle instance on another
> platform to talk to the gateway on the mainframe, but the gateway
still
> depends on SQLNET, which is an Oracle 7 client, and Oracle 9.2. WILL
NOT
> talk to Oracle 7. So for this shop, the Oracle Transparent Gateway is
> "morally, ethically, spiritually, physically, positively, absolutely,
> undeniably and reliably Dead!!" (quote from the Wizard of OZ)
>
> Now, the search is on for the world's absolutely cheapest ODBC
driver...
>
> Regards,
> Cathy Taddei
>
> ________________________________
>
> From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
> Behalf Of Krnic, Ivan B.
> Sent: Thursday, December 16, 2004 6:05 AM
> To: [login to unmask email]
> Subject: Re: Oracle Woes
>
>
> It is a bug. This is what is on Metalink:
> Bug 2394208
>
<http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_
> id=2394208&p_database_id=BUG> identifies that a change in IBM Media
> Manager in z/OS 1.3 and later
>
> causes Oracle Database Open failure. Oracle code has been changed to
> accomodate this.
>
> However, older versions that are no longer supported will not be
> corrected.
>
> Thus if you are planning to upgrade to z/OS 1.3 or 1.4, you should
> ensure you
>
> are running a version of Oracle that is eligible for corrective
> maintenance.
>
> Versions Affected
>
> ~~~~~~~~~~~~~~~~~
>
> 7.3, 8.0, 8.1.7.
>
> Platforms Affected
>
> ~~~~~~~~~~~~~~~~~~
>
> IBM z/OS Versions 1.3, 1.4.
>
>
>
> Description
>
> ~~~~~~~~~~~
>
> Database startup fails to open control file due to z/OS Media Manager
> interface failure.
>
> changes introduced with z/OS 1.3.
>
> Likelihood of Occurrence
>
> ~~~~~~~~~~~~~~~~~~~~~~~~
>
> Any "MPM"-based implementation of Oracle for z/OS (OS/390)
>
> Possible Symptoms
>
> ~~~~~~~~~~~~~~~~~
>
> Error messages on SYSLOG:
>
> Unable to initialize Media Manager interface for
<control_file_datafile>
>
>
> ORA-04217, FUNC=MMINIT, RS=0408400C
>
>
> Ivan Krnic
>
> DBA
>
>
>
>
> -----Original Message-----
> From: DB2 Data Base Discussion List
> [mailto:[login to unmask email]On Behalf Of Taddei, Cathy
> Sent: Wednesday, December 15, 2004 3:46 PM
> To: [login to unmask email]
> Subject: Oracle Woes
>
>
>
> We are unfortunately running the Oracle Transparent Gateway to
> access mainframe DB2 from Windows. Users sign on to an Oracle
instance
> on the mainframe (Oracle7 Server Release 7.3.3.6.2), and from there
> access the gateway to DB2. We are finally upgrading to z/OS 1.4, from
> OS/390 2.10. When I start Oracle under z/OS, I'm getting messages
like
> this:
>
> SVRMGR> ALTER DATABASE ORAD MOUNT;
> Unable to initialize Media Manager interface for CONTROL2.
> ORA-04217, FUNC=MMINIT, RS=0408400C
> Unable to initialize Media Manager interface for CONTROL1.
> ORA-04217, FUNC=MMINIT, RS=0408400C
> Statement processed.
> SVRMGR> ALTER DATABASE OPEN;
> Unable to initialize Media Manager interface for DB1 .
> ORA-04217, FUNC=MMINIT, RS=0408400C
> Unable to initialize Media Manager interface for DB2 .
> ORA-04217, FUNC=MMINIT, RS=0408400C
>
> Has anyone else encountered anything like this? Is there a
> remedy?
>
> Unfortunately, I cannot yet test the gateway itself. Is
anyone
> else running OTG Release 4.0.1.1.0 under z/OS?
>
> Thanks,
> Cathy Taddei
>
>
>
>
>
------------------------------------------------------------------------
------
>
> This email is confidential and may be legally privileged.
>
> It is intended solely for the addressee. Access to this email by
anyone else,
> unless expressly approved by the sender or an authorized addressee, is
> unauthorized.
>
> If you are not the intended recipient, any disclosure, copying,
distribution
> or any action omitted or taken in reliance on it, is prohibited and
may be
> unlawful. If you believe that you have received this email in error,
please
> contact the sender, delete this e-mail and destroy all copies.
>
>
=======================
======
>
>
------------------------------------------------------------------------
---------
> Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home
> page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select
> "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org.
> The IDUG List Admins can be reached at
[login to unmask email] Find
> out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm
>

------------------------------------------------------------------------
---------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that
page select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm


----------------------------------------------------------------------------
--

This email is confidential and may be legally privileged.

It is intended solely for the addressee. Access to this email by anyone
else, unless expressly approved by the sender or an authorized addressee, is
unauthorized.

If you are not the intended recipient, any disclosure, copying, distribution
or any action omitted or taken in reliance on it, is prohibited and may be
unlawful. If you believe that you have received this email in error, please
contact the sender, delete this e-mail and destroy all copies.

===
==

----------------------------------------------------------------------------
-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org.
The IDUG List Admins can be reached at [login to unmask email] Find
out the latest on IDUG conferences at http://conferences.idug.org/index.cfm


***********************************************************
CAUTION: This Message may contain confidential information intended
only for the use of the addressee named above. If you are not the
intended recipient of this message you are hereby notified that any use,
dissemination, distribution or reproduction of this message is prohibited.
If you received this message in error please notify Mail Administrators
immediately. Any views expressed in this message are those of the
individual sender and may not necessarily reflect the views of
Woolworths Ltd.
***********************************************************

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm