| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1136.1 | | chsr38.ch.oracle.com::ROHR | The Packers did it! | Mon Mar 24 1997 09:55 | 7 |
| If this is not supported in DBI are there any plans to support it? The
customer would really like to use this once they go in production, so I
would need to know what I can do to make this happen (product manager,
enhancement bug...).
Thanks,
Regina
|
| 1136.2 | Not sure what is happening... | BROKE::ABUGOV | | Tue Mar 25 1997 09:03 | 11 |
|
Hi Christina,
I'm not exactly sure what is happening with this rci request. Could
you define dbi_trace_flags to be "rci,exceptions,errors" and
dbi_trace_output to be a file that you can provide a pointer to (or it
it is short, post it).
Thanks,
Dan
|
| 1136.3 | The trace output | chsr38.ch.oracle.com::ROHR | The Packers did it! | Tue Mar 25 1997 14:15 | 172 |
| $ DELETE/SYMBOL/ALL
$ VRFY_SAVE = F$VERIFY(1)
$ DELETE SYS$SYSDEVICE:[SQLSRV$DEFLT]SQS_CHSR38_GBS00P000170.COM;1
$ DEFINE SQS$DBSERVER TRUE
$ DEFINE SYS$LOGIN "SYS$SYSDEVICE:[SQLSRV$DEFLT]"
$ SET DEFAULT SYS$LOGIN
$ DEFINE SYS$SCRATCH "SYS$SYSDEVICE:[SQLSRV$DEFLT]"
$ TMP = F$VERIFY(0)
Executing command: @SYS$COMMON:[SYSLIB]SQLSRV_SETVER.COM;2 7.0
Executing command: @SYS$COMMON:[SYSLIB]RDB$SETVER.COM;8 7.0 REMOTE SQLSRV
$ ARG1 = "SQLSRV_70000"
$ ARG2 = "1:1:245776"
$ ARG3 = "SYS$SYSDEVICE:[SQLSRV$DEFLT]SQS_CHSR38_GBS00P000170.LOG;"
$ ARG4 = ""
$ ARG5 = ""
$ ARG6 = "070000"
$ DBS$IMAGE_SYMBOL := $SYS$SYSTEM:sqlsrv_exec70.exe
$ DBS$IMAGE_SYMBOL "SQLSRV_70000" "1:1:245776" "SYS$SYSDEVICE:[SQLSRV$DEFLT]SQS_CHSR38_GBS00P000170.LOG;" "" "" "070000"
Unable to create trace output file 38_W2:[ROHR]DBI.LOG
. Trace output will be redirected to the terminal.8�
---EVENT BEG: RCI ------------------------------ Tue Mar 25 20:11:17.240 1997---
Entering FD_ATTACH_DATABASE
Input parameters:
DB Name :
utl_string_desc_t: (0x7EE27D10 : 2128772368):
length = 47
ptr -> "/type=dbi/dbname=38_w2:[pmslogs.log73552]gbs_do"
DB Handle : 00000000
DPB Length : 16 (0x00000010)
Security info length : 0 (0x00000000)
Database Parameter Block:
DPB_VERSION2
FACILITY_ALL
DPB2_DBKEY_SCOPE
DPB_DBKEY_SCOPE_TRANS
FACILITY_ALL
DPB2_REQUEST_SCOPE
DPB2_REQUEST_SCOPE_ATTACH
FACILITY_RDB_VMS
DPB2_CDD_MAINTAINED
---EVENT END: RCI ------------------------------ Tue Mar 25 20:11:17.350 1997---
---EVENT BEG: RCI ------------------------------ Tue Mar 25 20:11:26.380 1997---
Exiting FD_ATTACH_DATABASE
Output parameters:
DB Handle : 00010001
---EVENT END: RCI ------------------------------ Tue Mar 25 20:11:26.380 1997---
---EVENT BEG: RCI ------------------------------ Tue Mar 25 20:11:26.610 1997---
Entering FD_EXTENSION
Input parameters:
Extension index : 20
Handle : 00010001
Handle type : 1
Input buffer length : 22 (0x0016)
Result buffer length : 24 (0x0018)
Entering function PARSE_SET_TRANS
Input Buffer:
DEFAULT_TPB
Tpb_length: 2
MODULE_NAME
Name_length: 13
INFO_END
Entering function FD_PARSE_TPB
VERSION
WRITE
Exiting function FD_PARSE_TPB
Exiting function PARSE_SET_TRANS
---EVENT END: RCI ------------------------------ Tue Mar 25 20:11:26.690 1997---
---EVENT BEG: RCI ------------------------------ Tue Mar 25 20:11:26.730 1997---
Exiting FD_EXTENSION
---EVENT END: RCI ------------------------------ Tue Mar 25 20:11:26.730 1997---
---EVENT BEG: RCI ------------------------------ Tue Mar 25 20:11:26.740 1997---
Entering FD_DATABASE_INFO
Input parameters:
DB Handle : 00010001
Item list length : 5 (0x0005)
Result buffer length : 256 (0x0100)
Item list buffer:
DB_IMPLEMENTATION
3 1 23 1
DB_VERSION
13 1
11 "DBI V7.0-00"
DB_MULTISCHEMA
1 0
DB_CSET
12 CSET_DEC_MCS CSET_DEC_MCS CSET_DEC_MCS
INFO_END
---EVENT END: RCI ------------------------------ Tue Mar 25 20:11:26.760 1997---
---EVENT BEG: RCI ------------------------------ Tue Mar 25 20:11:26.760 1997---
Exiting FD_DATABASE_INFO
---EVENT END: RCI ------------------------------ Tue Mar 25 20:11:26.760 1997---
---EVENT BEG: RCI ------------------------------ Tue Mar 25 20:11:28.560 1997---
Entering FD_EXTENSION
Input parameters:
Extension index : 20
Handle : 00010001
Handle type : 1
Input buffer length : 22 (0x0016)
Result buffer length : 24 (0x0018)
Entering function PARSE_SET_TRANS
Input Buffer:
DEFAULT_TPB
Tpb_length: 2
MODULE_NAME
Name_length: 13
INFO_END
Entering function FD_PARSE_TPB
VERSION
WRITE
Exiting function FD_PARSE_TPB
Exiting function PARSE_SET_TRANS
---EVENT END: RCI ------------------------------ Tue Mar 25 20:11:28.640 1997---
---EVENT BEG: RCI ------------------------------ Tue Mar 25 20:11:28.640 1997---
Exiting FD_EXTENSION
---EVENT END: RCI ------------------------------ Tue Mar 25 20:11:28.640 1997---
------------EVENT BEGIN: EVENT_LOG at Tue Mar 25 1997 20:11:28.901-------------
%SQLSRV-I-EVENT_LOG, event logged at line 2387 in file SRVEXE.C;1
%SQLSRV-E-LWCCONNERRUSER, Error creating a SQL connect for username: ROHR
%RDB-F-UNS_RCI, RCI call rdb_set_authorization is not supported by DataBase Integrator
------------EVENT END : EVENT_LOG at Tue Mar 25 1997 20:11:28.929-------------
------------EVENT BEGIN: EVENT_LOG at Tue Mar 25 1997 20:13:25.838-------------
%SQLSRV-I-EVENT_LOG, event logged at line 9088 in file CMD.C;1
%SQLSRV-I-SM_EXECSHUT, Shutting down executor GBS00P0001
------------EVENT END : EVENT_LOG at Tue Mar 25 1997 20:13:25.864-------------
---EVENT BEG: RCI ------------------------------ Tue Mar 25 20:13:25.900 1997---
Entering FD_DETACH_DATABASE
Input parameters:
DB Handle : 00010001
---EVENT END: RCI ------------------------------ Tue Mar 25 20:13:25.900 1997---
---EVENT BEG: RCI ------------------------------ Tue Mar 25 20:13:26.260 1997---
Exiting FD_DETACH_DATABASE
---EVENT END: RCI ------------------------------ Tue Mar 25 20:13:26.260 1997---
SQLSRV$DEFLT job terminated at 25-MAR-1997 20:13:26.95
Accounting information:
Buffered I/O count: 433 Peak working set size: 21344
Direct I/O count: 292 Peak page file size: 108464
Page faults: 2609 Mounted volumes: 0
Charged CPU time: 0 00:00:02.76 Elapsed time: 0 00:02:17.65
|
| 1136.4 | Any news? | chsr38.ch.oracle.com::ROHR | The Packers did it! | Tue Apr 01 1997 10:18 | 10 |
| Any news on this?
Is is normal that it doesn't work? If yes what can I do to get this
feature?
If it is not normal then please advise if I have to open a bug.
Thanks,
Regina
|
| 1136.5 | being looked at | BROKE::ABUGOV | | Wed Apr 02 1997 13:23 | 9 |
|
Hi Regina,
Someone is looking at this (but they have other development
deliverables too so please bear with us).
Thanks,
dan
|
| 1136.6 | Recreated on our system here. | BROKE::BITHER | | Wed Apr 02 1997 17:58 | 30 |
| Hi Regina,
DBI v7.00
Rdb v7.0-01
SQL/Serv v7.00
I was able to recreate your problem today exactly as you described.
I don't think it is possible at this time to attach to a dbi database
using a v7 database class service.
What works:
generic service - to an Rdb database.
generic service - to a DBI database.
database class service - to an Rdb database.
What fails:
database class service - to a DBI database.
Fails with the error:
[Oracle][ODBC][Rdb]%RDB-F-UNS-RCI, RCI call rdb_set_authorization is
not supported by DataBase Integrator (#-1)
I have everything configured on our system here which is the same
system engineering (see previous reply) is using to work on this problem
so am sending them the configuration info.
Diane
|
| 1136.7 | Bug 478294 | CHSR38::RROHR | Cajun? Zeydeco? Both! | Mon Apr 14 1997 06:33 | 4 |
| Customer wants to use this in production, so he needs to know if this
is a restriction or if this is a bug with a possible fix.
Bug 478294
/Regina
|
| 1136.8 | It is a restriction at this time... | BROKE::ABUGOV | | Mon Apr 14 1997 10:21 | 13 |
|
Hi Regina,
The supported method for connecting using Rdb and a database class
service is not available in DBI (it is a restriction).
We are trying to determine why when the security mechanism was
circumvented the unsupported RCI message was returned. That is the
what we are looking at at this point in time.
Sorry,
Dan
|
| 1136.9 | | CHSR38::RROHR | Cajun? Zeydeco? Both! | Mon Apr 14 1997 12:50 | 22 |
| Hi Dan,
>>The supported method for connecting using Rdb and a database class
^^^^^^^^^
>>service is not available in DBI (it is a restriction).
Is there an unsupported method? Just in case. ;-)
>>We are trying to determine why when the security mechanism was
>>circumvented the unsupported RCI message was returned. That is the
>>what we are looking at at this point in time.
I don't feel I have circumvented security mechanisms?
Is the restriction documented somewhere so that I can at least show a
piece of paper or documentation to this unhappy fellow?
As it is a restriction, will it be lifted?
Thanks,
Regina
|
| 1136.10 | I wish I could make him happy... | BROKE::ABUGOV | | Tue Apr 15 1997 10:02 | 37 |
|
Hi Regina,
The mechanism used by SQL Services to attach to rdb database class
servers was invented and implemented by those groups. I thought I read
in the SQL Services notes file a warning about the work-around you have
implemented regarding security and granting the rights identifier to
a user accessing the dbi database (I could have misinterpreted it though).
At this point it is a restriction, undocumented because we just found
out about it with "this unhappy fellow".
Sorry,
Dan
<<< NOMAHS::DISK$NOMAHS1:[NOTES$LIBRARY]SQL_SERVICES.NOTE;1 >>>
-< SQL/Services Forum >-
================================================================================
Note 2173.9 Database service priv problem with DO 9 of 9
ORASQS::OXBURY "Oracle Corporation, Rdb Desktop Gro" 14 lines 24-MAR-1997 09:45
-< DON'T grant that Ident to any accnts/feature not supported by DB >-
--------------------------------------------------------------------------------
The previous note I entered was an attempt to briefly describe the
INTERNALS that SQL/Services uses to handle database services with
database authorization by connect user, so as to explain that as far as
I know, DBI, does NOT support the interface that Rdb provides to
SQL/Services to support database services with database authorization
by connect user. In this respect, RDB$TRUSTED_USER is an identifier
that SQL/Services dynamically and automatically grants to executor
PROCESSES for database services with database authorization by connect
user; its not something that customers have to deal with. DO NOT grant
this identify to any account; doing so will allow that account to do
anything with any database on your system, given the knowledge of how
to do it.
Si
|