AQ PL/SQL registered notifications
Suppose I want to see what registered notifications exist for AQ plsql notifications.
What I'm talking about are those notifications to PL/SQL callback procedures that have been registered using DBMS_AQ.REGISTER.
I've searched and searched for data dictionary information about this but cannot find it.
How can I use DBMS_AQ.UNREGISTER if I do not know what is already registered ?
I would have thought that SYS.ALL_STREAMS_MESSAGE_CONSUMERS would have been a good guess but it doesn't have any rows and I have a working PLSQL notification active.
Database is v10.2.
Anyone know where to find this information ?
Thanks.
Hello,
Unfortunately there is not a user view which is definitely an oversight. As suggested you could be granted the necessary privilges on sys.reg$ to overcome this.
However, this whole area has been re-invigorated by the Database Change Notification feature which came in in 10.2. So much so that in 11.1 onwards you have the SUBSCRREGISTRATIONS and other v$ views as per http://download.oracle.com/docs/cd/B28359_01/server.111/b28420/aq_views.htm#sthref1151.
The EMON process architecture has been changed to the now standard Coordinator/slave architecture as well. So with this investment in development in this area the robustness, scalability and diagnosability is improving.
Thanks
Peter
Similar Messages
-
SQL Server Notification Services Removed from SQL Server 2008
It comes as no surprise to us that 2008 will not be supporting notification services. Several years ago our company developed our product line of alerting applications and gave some long and serious thought into using SQL Notification services.
Besides the fact that the NS desktop alerting component itself was rather bland/limited, (an acknowledge button, image, hyperlink) at the time it just made no sense to create a core component of the business plan around such a 3rd party dependent widget.
While a look at this MS page shows only a few companies who have built alerting systems around NS,
http://www.microsoft.com/sql/technologies/notification/partners/appsoftware.mspx
….there is actually quite a few companies who have done this and must now consider a total rewrite of their alert system.
Quite frankly, looking forward at MS's new family of Communications servers,
http://msdn2.microsoft.com/en-us/office/aa905499.aspx
I am not sure that things are changing much.
"Welcome to the Microsoft Office Live Communications Server developers' home on MSDN. Live Communications Server 2005 provides your business with an enterprise-ready instant messaging, presence awareness, and an extensible platform that connects people, information, and business processes—enabling better decisions faster."
Remember this?
MSN Buys MessageCast for Real-Time Alerts
http://www.eweek.com/c/a/Messaging-and-Collaboration/MSN-Buys-MessageCast-for-RealTime-Alerts/
MessageCast was a serious product on the up. They sold out and poof. The whole fiasco was a joke.
As it pertains to alerting platforms, the good call just may be having a architecture that is somewhat autonomous ( i.e. Ok, perhaps Windows OS, .Net Framework and SQL Server as prerequisites is ok) to MS embedded components and not reliant on “Live Server" licenses. Seems like just a better bet hands down all day long.
I can tell you that about 5% of all alerts our clients create are sent to inform end users “Exchange is Down”. It’s hard to get a OutLook Desktop Alert when Exchange is down.
So, an alert system designed from scratch in-house (the hard way) may just be the heads up alert your customer needs to see. If for nothing else, you can control your products destiny….unless of course MS Windows is made obsolete. <wink> Unlikely. Hey....without MS products, we would not be in business. They make some of the best software in the world. But that does not mean your campany is not capable of the same.I'm coming to the discussion of the fate of Notification Services a bit late as it is now December. It is my view that Microsoft should rethink its position on Notification Services, and should continue to support and evolve it until such time as it might be migrated to the future "alerting" solution Microsoft devises for at least the following 2 reasons:
(1) Notification Services addresses an enterprise application integration need complementary to Microsoft's web service strategy. This is a place Microsoft has not gone before, but needs to go. Why? EAI vendors won't modify their infrastructure to make them web service oriented ... they can't because it is legacy. Instead, they try to buy something and attach it to legacy ... but that doesn't work too well. Microsoft already has started/built greenfield. Further, Microsoft has commoditized such so that with notification services and its other .NET-based products (at least they evolve to such) a full complement of architectural components is being or has been assembled. Why would Microsoft make such an investment ... across the portfolio of server products ... and then back off of it? Microsoft has not been in the enterprise space before to the degree it has wished. It has intimated, at least, that it will be at the periphery with its variety of services and products. An integration broker is necessary for success at the periphery, and it provides a bridge to the enterprise back office that has the property of loose coupling, which is both good for Microsoft and its clients.
(2) Microsoft claims to be working to develop a server platform suitable to provision notification services. This server platform could be productized as Microsoft intends, and then notification services could be made to work on that platform and then it could be open sourced. If Microsoft intends to provide a kind of application server foundation that would make it possible for non-Microsoft development teams to build out services on a Microsoft stack that can be hosted with the same set of services as, say, IIS, Biztalk, SQL Server, etc., then it seems that Notification Services could easily be migrated to this server framework once such is ready for prime time. Functional expansion of such could be accomplished by an open source community if Microsoft chooses to not further extend it on its own dime ... maybe even on its own nickel.
I've read some of the reasons justifying Microsoft's rationale to discontinue its Notification Services product line. One was that not many people used it. Blogs have listed a number of companies that have used it. The number may not be to the scale Microsoft would like ... one could look at Biztalk and suggest that Workflow Foundation represents Microsoft's belief that Biztalk too should be deprecated. Maybe so. But the strategy Microsoft is taking with workflow does not drop support for a core architectural capability. Why not keep Notification Services and give people time to learn how to architect in enterprise fashion with Microsoft infrastructure? Why not use it to seed an open source community? It probably costs you little ... and you have an open source community option that could get Microsoft further into an enterprise than it has previously been ... right into the middle ... leveraging Microsoft web service innovations in spades at substantially less cost than traditional EAI vendors, IBM, and other competitors could afford. People have to learn how to use Microsoft products in an enterprise context ... aside from specialized applications and OS vmware, what products have you put out that systematize infrastructure?
I've also heard that Microsoft is considering incorporation of Notification Services as part of Reporting Services. Please pardon me but that seems ack basswards ... events are not reports, but reports could be events if you view reports as correlations over critical business activities instead of some statically produced bit of information to be shoved off into someone's mailbox or file system or even web site. Reports are static. Events are part of a dynamic and learning enterprise platform. Isn't that what you're attempting to build infrastructure for? Isn't that exactly what Microsoft needs to secure its position at the back of an enterprise just as it has the front?
Please reconsider your position. And please contact me at tommy at zipa dot deedoodah dot com to discuss. I'm as opinionated as everyone else, and I think you have a good product here that you're throwing away. If you don't want it, I will take it ...
Sincerely,
Tom Winans -
Regarding sql server notification service
i never use sql server notification service. so i like to know what it does. does it notify when data changed? suppose i have one win apps by which our employee insert/update/delete data. i want that when data will be inserted/updated/deleted then this notification
service notify my win apps that data change and also provide technique to know which data change or inserted or delete. i use sql dependency but it has draw back like it can only notify client about something has happened but never say like which data is inserted
or updated or deleted.
anyone can guide me how to notify my win client from sql server with changed data like push notification with data to win client. thankscan u please point me to any good article which help me to write that kind of trigger which can capture data change and push the change to client. thanks
I couldn't find an article with a cursory search so I created the example below to illustrate this basic technique that you can customize and extend for your purposes. The trigger creates an XML document with the before/after images of the inserted/updated/deleted
rows. The application executes the change notification target service proc in a loop to receive change messages as they become available.
This method will work for a single application instance that receives change notifications. If you have multiple users, I suggest a mid-tier service to receive these notifications and then multicast to clients using a publish/subscribe pattern.
In the case of frequent data changes, it would be better to use a single long-running conversation with the conversation handle saved to a state table instead of starting a new conversation for each message in order to reduce service broker overhead.
Note that the trigger will write messages to the queue regardless of whether an application is listening for messages. For that reason, it would generally be best to run the mid-tier service continuously or at least consume/ignore all of the pending
messages at startup.
Be aware that there are a number of variations of this general pattern but I think this should get you started. Post questions specific to Service Broker to the related forum:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlservicebroker
CREATE DATABASE ExampleDatabase;
ALTER AUTHORIZATION ON DATABASE::ExampleDatabase TO sa;
ALTER DATABASE ExampleDatabase SET ENABLE_BROKER;
GO
USE ExampleDatabase;
GO
CREATE TABLE dbo.Product(
ID varchar(50) NOT NULL
CONSTRAINT PK_Product PRIMARY KEY
, ProductName varchar(50)
, ProductDescription varchar(1000)
GO
CREATE TRIGGER TR_Product
ON dbo.Product
FOR INSERT, UPDATE, DELETE
AS
DECLARE
@ConversationHandle uniqueidentifier
,@ChangedRows xml;
SELECT @ChangedRows = (
SELECT
SELECT ID, ProductName, ProductDescription
FROM dbo.Product
FOR XML PATH('Before'), TYPE)
SELECT ID, ProductName, ProductDescription
FROM dbo.Product
FOR XML PATH('After'), TYPE)
FOR XML PATH('Changes'), TYPE
BEGIN Dialog @ConversationHandle
FROM SERVICE [ProductChangeNotificationInitiatorService]
TO SERVICE 'ProductChangeNotificationTargetService'
ON CONTRACT [ProductChangeNotificationContract]
WITH ENCRYPTION = OFF;
SEND ON CONVERSATION @ConversationHandle
MESSAGE TYPE [ProductChange]
(@ChangedRows);
GO
CREATE MESSAGE TYPE [ProductChange] VALIDATION = WELL_FORMED_XML;
CREATE CONTRACT [ProductChangeNotificationContract](
[ProductChange] SENT BY INITIATOR
CREATE TABLE dbo.ProductChangeNotificationErrors(
ErrorTime datetime NOT NULL
,conversation_handle uniqueidentifier NOT NULL
,service_name sysname
,message_type_name nvarchar(256) NOT NULL
,message_body varbinary(MAX) NULL
GO
CREATE PROCEDURE dbo.usp_CleanupProductChangeNotificationInitiatorQueue
AS
SET NOCOUNT ON;
DECLARE
@conversation_handle uniqueidentifier = '00000000-0000-0000-0000-000000000000'
,@service_name sysname
,@message_type_name nvarchar(256)
,@message_body varbinary(MAX)
,@description nvarchar(3000);
WHILE @conversation_handle IS NOT NULL
BEGIN
SET @conversation_handle = NULL;
WAITFOR (
RECEIVE TOP (1)
@conversation_handle = conversation_handle
,@service_name = service_name
,@message_type_name = message_type_name
,@message_body = message_body
FROM dbo.ProductChangeNotificationInitiatorQueue)
,TIMEOUT 1000;
IF @conversation_handle IS NOT NULL
BEGIN
IF @message_type_name = N'http://schemas.microsoft.com/SQL/ServiceBroker/EndDialog'
BEGIN
END CONVERSATION @conversation_handle;
END
ELSE
BEGIN
INSERT INTO dbo.ProductChangeNotificationErrors(
ErrorTime
,conversation_handle
,service_name
,message_type_name
,message_body)
VALUES(
GETDATE()
,@conversation_handle
,@message_type_name
,@service_name
,@message_body)
SET @description = 'Unexpected message type ' + @message_type_name + ' received';
END CONVERSATION @conversation_handle WITH ERROR = 1 DESCRIPTION = @description;
END;
END;
END;
GO
CREATE QUEUE ProductChangeNotificationInitiatorQueue
WITH ACTIVATION (
PROCEDURE_NAME = dbo.usp_CleanupProductChangeNotificationInitiatorQueue,
MAX_QUEUE_READERS = 1,
EXECUTE AS SELF);
CREATE SERVICE [ProductChangeNotificationInitiatorService]
ON QUEUE ProductChangeNotificationInitiatorQueue ([ProductChangeNotificationContract]);
CREATE QUEUE ProductChangeNotificationTargetQueue;
CREATE SERVICE ProductChangeNotificationTargetService
ON QUEUE dbo.ProductChangeNotificationTargetQueue (ProductChangeNotificationContract);
GO
CREATE PROCEDURE dbo.usp_ProductChangeNotificationTargetService
@Timeout int = 5000
AS
SET NOCOUNT ON;
SET XACT_ABORT ON;
DECLARE
@conversation_handle uniqueidentifier
,@service_name sysname
,@message_type_name nvarchar(256)
,@message_body varbinary(MAX)
,@description nvarchar(3000);
WAITFOR (
RECEIVE TOP (1)
@conversation_handle = conversation_handle
,@service_name = service_name
,@message_type_name = message_type_name
,@message_body = message_body
FROM dbo.ProductChangeNotificationTargetQueue)
,TIMEOUT @Timeout;
IF @conversation_handle IS NOT NULL
BEGIN
SELECT CAST(@message_body AS xml) AS ChangedRows;
END CONVERSATION @conversation_handle;
END;
GO
Dan Guzman, SQL Server MVP, http://www.dbdelta.com -
PL/SQL Callback notification with aq$_jms_text_message
Hi,
i want to set up a notfication for a pl/sql callback procedure. The message in my queue is enqueued via propagation from another instance. This is my setup (using oracle 10.2.0.3):
-------- the queue (multiconsumer): --------------
begin
dbms_aqadm.create_queue_table(queue_table => 'zmon_evt_in_qtable',queue_payload_type => 'sys.aq$_jms_text_message', multiple_consumers => true);
dbms_aqadm.create_queue(queue_name => 'zmon_evt_in_queue',queue_table => 'zmon_evt_in_qtable' );
dbms_aqadm.start_queue( queue_name =>'zmon_evt_in_queue' );
end;
-------- the callback-procedure (simply inserting an entry in a table called 'test'): --------------
create or replace procedure evt_in_callback(
context IN RAW,
reginfo IN SYS.AQ$_REG_INFO,
descr IN SYS.AQ$_DESCRIPTOR,
payload IN VARCHAR2,
payloadl IN NUMBER) is
begin
insert into test(textfeld) values ('RECEIVED!');
commit;
end evt_in_callback;
-------- the subscriber: --------------
begin
dbms_aqadm.add_subscriber(queue_name => 'zmon.zmon_evt_in_queue',
subscriber => sys.aq$_agent('zmon_evt_in_subscriber',null,null));
end;
-------- the notification: --------------
declare
reginfo sys.aq$_reg_info;
reg_list sys.aq$_reg_info_list;
begin
reginfo := sys.aq$_reg_info(name => 'zmon.zmon_evt_in_queue:zmon_evt_in_subscriber',
namespace => DBMS_AQ.NAMESPACE_AQ,
callback => 'plsql://zmon.evt_in_callback',
context => HEXTORAW('FF')
reg_list := sys.aq$_reg_info_list(reginfo);
DBMS_AQ.REGISTER(reg_list => reg_list,
reg_count => 1);
end;
The callback-procedure is not fired on arrival of a message in the queue. But i can see the the appropriate notfication-entry in sys.reg$.
Any suggestions why this doesn't work ?
BTW: can anybody tell me the meaning of the context-Parameter in the aq$_reg_info-Type ? Everybody uses HEXTORAW('FF'), but I don't understand what that means...
Jens
Edited by: dschenzl on Jun 4, 2009 11:13 AMFinally, it's done.
The subscriber used in the propagation has to be the notification-subscriber (zmon_evt_in_subscriber). I used another subscriber, which was not registered for notification.
I found the solution in this thread: Callback trouble from mesage via propagated message.
Two days filled up with frustrating work - man, how i hate that...
Greetings to the community,
Jens -
PL/SQL AQ notification works in XE but not in our Enterprise Edition
Hello,
I am trying to get a Queue up and working and have ran through several examples, but I cannot get the Notify to work in our development environment but it works just fine in my local XE instance.
Below is the code that WORKS in XE but does not call the procedure in the Enterprise Edition of Oracle:\
Please note I may manually DBMS_AQ.DEQUEUE the queued item -- that works just fine, but the intent is the have it notify the procedure (this is still hashing out this technology so keep that in mind during critiquing).
What is different between XE and Enterprise Edition in these regards or what is it I should check?
(I got the job_queue_processes increased as noted in the below)
GRANT EXECUTE ON dbms_aq TO aq;
GRANT EXECUTE ON dbms_aqadm TO aq;
GRANT CONNECT, RESOURCE, aq_administrator_role TO aq;
begin
dbms_aqadm.grant_system_privilege('ENQUEUE_ANY','aq',FALSE);
dbms_aqadm.grant_system_privilege('DEQUEUE_ANY','aq',FALSE);
commit;
end;
drop procedure demo_queue_callback_procedure;
BEGIN
DBMS_AQADM.STop_QUEUE ( queue_name => 'aq.streams_queue_1' );
DBMS_AQADM.DROP_QUEUE ( queue_name => 'aq.streams_queue_1' );
DBMS_AQADM.DROP_QUEUE_TABLE ( queue_table => 'aq.streams_queue_1_table'
,FORCE =>TRUE );
END;
BEGIN
DBMS_AQADM.CREATE_QUEUE_TABLE (
queue_table => 'aq.streams_queue_1_table'
,queue_payload_type => 'aq.APP_INFO'
,multiple_consumers => TRUE );
DBMS_AQADM.CREATE_QUEUE (
queue_name => 'aq.streams_queue_1',
queue_table => 'aq.streams_queue_1_table'
DBMS_AQADM.START_QUEUE (
queue_name => 'aq.streams_queue_1'
END;
CREATE TABLE aq.queue_message_table
( message VARCHAR2(4000) , ins_date date default sysdate);
CREATE or replace PROCEDURE aq.demo_queue_callback_procedure(
context RAW,
reginfo SYS.AQ$_REG_INFO,
descr SYS.AQ$_DESCRIPTOR,
payload RAW,
payloadl NUMBER
) AS
r_dequeue_options DBMS_AQ.DEQUEUE_OPTIONS_T;
r_message_properties DBMS_AQ.MESSAGE_PROPERTIES_T;
v_message_handle RAW(16);
o_payload aq.APP_INFO;
BEGIN
r_dequeue_options.msgid := descr.msg_id;
r_dequeue_options.consumer_name := descr.consumer_name;
DBMS_AQ.DEQUEUE(
queue_name => descr.queue_name,
dequeue_options => r_dequeue_options,
message_properties => r_message_properties,
payload => o_payload,
msgid => v_message_handle
INSERT INTO aq.queue_message_table ( message )
VALUES ( '[' || o_payload.parameter || ';' || o_payload.value || ';' || to_char(o_payload.dte,'ddMONyy:hh:mi:ss') ||']' );
COMMIT;
END;
BEGIN
DBMS_AQADM.ADD_SUBSCRIBER (
queue_name => 'aq.streams_queue_1',
subscriber => SYS.AQ$_AGENT(
'aq_queue_subscriber',
NULL,
NULL )
DBMS_AQ.REGISTER (
SYS.AQ$_REG_INFO_LIST(
SYS.AQ$_REG_INFO(
'streams_queue_1:aq_queue_subscriber',
DBMS_AQ.NAMESPACE_AQ,
'plsql://aq.demo_queue_callback_procedure',
HEXTORAW('FF')
1
END;
DECLARE
r_enqueue_options DBMS_AQ.ENQUEUE_OPTIONS_T;
r_message_properties DBMS_AQ.MESSAGE_PROPERTIES_T;
v_message_handle RAW(16);
o_payload aq.app_info;
vreclst DBMS_AQ.AQ$_RECIPIENT_LIST_T;
BEGIN
o_payload := aq.app_info('msg4',4,sysdate);
--vreclst(1):= sys.aq$_agent('ANYONE','', null);
--r_message_properties.recipient_list:= vreclst;
DBMS_AQ.ENQUEUE(
queue_name => 'aq.streams_queue_1',
enqueue_options => r_enqueue_options,
message_properties => r_message_properties,
payload => o_payload,
msgid => v_message_handle
COMMIT;
END;
select * from aq.queue_message_table ;
SELECT *
FROM aq.aq$streams_queue_1_table;
set serveroutput on
DECLARE
r_dequeue_options DBMS_AQ.DEQUEUE_OPTIONS_T;
r_message_properties DBMS_AQ.MESSAGE_PROPERTIES_T;
v_message_handle RAW(16);
o_payload aq.app_info;
BEGIN
--r_dequeue_options.dequeue_mode := DBMS_AQ.BROWSE;
r_dequeue_options.consumer_name := 'aq_QUEUE_SUBSCRIBER';
DBMS_AQ.DEQUEUE(
queue_name => 'aq.streams_queue_1',
dequeue_options => r_dequeue_options,
message_properties => r_message_properties,
payload => o_payload,
msgid => v_message_handle
DBMS_OUTPUT.PUT_LINE(
'*** message is [' || o_payload.parameter || ';' || o_payload.value || '] ***'
commit;
END;
select * from dba_queue_schedules ;
select * from dba_objects;
SELECT *
FROM v$parameter
WHERE name = 'aq_tm_processes'
OR name = 'job_queue_processes';
job_queue_processes = 10;
aq_tm_processes = 0;
SELECT *
FROM v$parameter
WHERE name = 'aq_tm_processes'
OR name = 'job_queue_processes';
in XE
aq_tm_processes => 0
job_queue_processes => 10
Ora Type:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
CORE 11.2.0.1.0 Production
TNS for IBM/AIX RISC System/6000: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
in XE
Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production
PL/SQL Release 11.2.0.2.0 - Production
CORE 11.2.0.2.0 Production
TNS for 32-bit Windows: Version 11.2.0.2.0 - Production
NLSRTL Version 11.2.0.2.0 - Production
the
job_queue_processes => 4Got it working,
in running this
SELECT owner, queue_name, queue_table, consumer_name
FROM dba_queue_subscribersI saw that there was an initial queue consumer that was overlapping, I dropped the initial queue and recreated all and it now works. -
Creating SQL SERVER notification from Oracle Enterprise Manager to Outlook
Hi,
I have a requirement to configure OEM to send an email via outlook when the SQL Server fails over to the standby server. Currently we receive emails if the CPU is high or if the agent is down etc. However, I was wondering if we could send an email when the primary sql server switches over to the mirrored server for whatever reason. This has happend in the past and we were unaware that the primary and mirrored server roles were switched. Is this possible?
Thanks,
JAs far as i know, currently we do not support this out of the box. I will file an ER for it. That said, if you are using EM 12c, then you can define a metric extension to create your own metric for failover/switch notifications.
Useful links:
http://www.oracle.com/technetwork/oem/em12c-screenwatches-512013.html#monitoring
http://docs.oracle.com/cd/E24628_01/doc.121/e24473/metric_extension.htm#CACJABFC -
How to register notification using NSDistributedNotification ?
I am working on Xcode4.2 and IOS 5 . I had gone through the Notification document, I have seen we can listen to other application's event using NSDistributedNotification.I tried to register with NSDistributionNotification. But i am getting compilation error. Later i checked framework class, there i don't find the NSDistributedNotification.h. Where can i found this class and how to register with this register the notification using NSDidtributedNotification.
Thanks
PushpaCompare the Mac and iOS developer library Notification Centers. Despite the fact the document text is identical, including references to NSDistributedNotificationCenter, notice the OBJECTIVE-C REFERENCE heading in the Table of Contents includes NSDistributedNotificationCenter only in the Mac developer library.
Mac
https://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/Notifica tions/Articles/NotificationCenters.html
iOS
https://developer.apple.com/library/ios/#documentation/Cocoa/Conceptual/Notifica tions/Articles/NotificationCenters.html -
SQL Blocking notification - at high monitoring level and holding many threads in Sharepoint 2010
I am getting the following error in our SharePoint 2010 environment:
Unexpected PortalSiteMapProvider was unable to fetch current node, request
Account Pipeline Dashboard/EditForm.aspx, message: Thread was being aborted.
Any ideas?
-KashThere could be multiple reasons for this, one possible reason is that your application pool account does not have full permissions to read the complete site collection.
Identify your web apps' app pool account using inetmgr
Login to central site administration
Go to Application management > Policy for web application
Choose the web application where the inaccessible site collection exists
Add a full control policy for the app pool account
Try below command:
$wa = Get-SPWebApplication -Identity "http://intranet.mysite.com"
$wa.Properties["portalsuperuseraccount"] = "i:0#.w|pro1766\sp_superuser_cache" $wa.Properties["portalsuperreaderaccount"] = "i:0#.w|pro1766\sp_superreader_cache"
$wa.Update()
Also try below hotfix
http://blogs.msdn.com/b/joerg_sinemus/archive/2013/02/12/february-2013-sharepoint-2010-hotfix.aspx
If this helped you resolve your issue, please mark it Answered -
PL/SQL notification / DBMS_AQ.REGISTER
There have been a number of discussions on this forum about PL/SQL notifications. I'm running
into the same problem:
- create the notification procedure
- register the procedure
- enqueue a message
- NOTHING HAPPENS
It seems that the notification procedure is not executed.
The discussions on this forum were all inconclusive. Did anybody get this to work? If yes, can
you post an example (i.e. a script that creates the queue, create the procedure, registers the
procedure and enqueues a message)?
Is there a table/view that contains the registrations?
What system parameters are relevant to this functionality?
Where are errors in calling the notification procedure logged?There are few problems that I can see with your code.
Your callback procedure header should look like this:
create or replace procedure QCallBack1(
context RAW,
reginfo SYS.AQ$_REG_INFO,
descr SYS.AQ$_DESCRIPTOR,
payload VARCHAR2,
payloadl NUMBER) is
BEGIN
END ;
And your callback notification does not include the name of the QUEUE subscriber. The first parameter
to the AQ$_REG_INFO should be of this format: <QUEUE ADMIN>.<QUEUE_NAME>:<QUEUE SUBSCRIBER>
When you say this:
sys.aq$_reg_info('myprofile.Que1',dbms_aq.namespace_aq, 'plsql://myprofile.QCallBack1', hextoraw('FF'));
You are not putting the name of the queue subscriber into the first parameter.
Also, Your callback notification URL must be like this:
'plsql://<user containing the callback proc>.<name of the callback proc>?PR=1'
Note that if the callback procedure is in another schema, you must grant EXECUTE priv. to the user
where the QUEUE has been setup.
Hallo,
I have got the same problem as Erwin Groenendal. I wrote single user que and procedures to enque and deque as simple as I can do.
pseudocode:
1. create and start que - no error
2. create proc for callback in pl/sql - no error
3. register callback - no error
4. enque message - noerror (no callback called)
5. deque message - noerror
in callback procedure I am writing into my own table with one varchar2 column to determine if the callback was processed.
My register procedure looks like: (pseudocode point 3)
procedure Register
is
XRegProc sys.aq$_reg_info;
XRegList sys.aq$_reg_info_list;
begin
XRegProc := sys.aq$_reg_info('myprofile.Que1', dbms_aq.namespace_aq, 'plsql://myprofile.QCallBack1', hextoraw('FF'));
XRegList := sys.aq$_reg_info_list(XRegProc);
dbms_aq.register(XRegList, 1);
end;
in definition variable XRegProc I tryed all possibilities like:
'plsql://myprofile.QCallBack1'
'plsql://myprofile.QCallBack1?PR=0'
'plsql://QCallBack1'
'plsql://myprofile.QCallBack1'
and so on.
The Callback looks like:
procedure QCallBack1(
context out raw,
reginfo out sys.aq$_reg_info,
descr out sys.aq$_descriptor,
payload out raw,
payloadl out number)
is
begin
insert into MyOwnTable (my_text) values ('Message notification callback called.');
commit;
end;
with compilation i have not problems. I am running oracle 9i release 2.
the enque procedure looks like:
procedure put(
APayload in raw,
ACorrelation in varchar2)
is
XEnq_opts dbms_aq.enqueue_options_t;
XMsg_props dbms_aq.message_options_t;
XMsg_id raw(16);
begin
XMsg_props.correlation := ACorrelation;
dbms_aq.enqueue('Que1', XEnq_opts, XMsg_props, APayload, XMsg_id);
commit;
end;
All rights are corectly sets under SYSTEM user.
Please help somebody why it does not work. I not see problem byt I need to call some procedure when new message arive into que. I need to have paralel process, I can not solve it with loops and so on.
Thanks for every ideas. In next week I can show you source code. Today I can not.
Regards, Zdenek.
For Oracle9i and above DBMS_AQ.REGISTER can be used for PL/SQL callback notification.
If running earlier version of Oracle, use DBMS_AQ.LISTEN to get a similar functionality.
It depends upon the URL that you specify while registering, that decides if callback will be executed or
not.
If you post the code fragment(s) of how you created the notification procedure and how you registered it,
maybe we can look to see if it is correct.
There have been a number of discussions on this forum about PL/SQL notifications. I'm running
into the same problem:
- create the notification procedure
- register the procedure
- enqueue a message
- NOTHING HAPPENS
It seems that the notification procedure is not executed.
The discussions on this forum were all inconclusive. Did anybody get this to work? If yes, can
you post an example (i.e. a script that creates the queue, create the procedure, registers the
procedure and enqueues a message)?
Is there a table/view that contains the registrations?
What system parameters are relevant to this functionality?
Where are errors in calling the notification procedure logged? -
Issue in Oracle 11g Database Change Notification for Java application
Hi,
I am trying to use Oracle's Database Change Notification in Java application.
I followed the sample application (+DBChangeNotification.java+ , Example 29-2), provided in the following link:
+[http://download.oracle.com/docs/cd/B28359_01/java.111/b31224/dbmgmnt.htm#CHDEJECF]+
I am able to see that the Registration of the SQL query is successful.
But, when I do changes to the table registered, notifications are not received in the Listener class (+DCNDemoListener.java+).
Ideally, the method DCNDemoListener.onDatabaseChangeNotification() should be invoked on any insert/update to the registered table. But this method is not getting invoked.
The execution has stopped in the following line of DBChangeNotification.java Class.
this.wait();
+==> The application was WAITing indefinitely in this line, as the NOTIFY() from DCNDemoListener.java was not executed.+
I am using VPN to connect to Oracel server. Remote Oracle Server is protected my firewall. Is this the reason for not sending the notifications from Oracle server?
The version of software used are given below:
Oracle Client - Oracle 11.1.0
JDK - 1.6
Oracle JDBC Driver - ojdbc6.jar
Can someone help me to resolve this issue?
Thanks in Advance.
Regards
Sam
Edited by: Ponsu on Apr 7, 2011 10:41 PMHi,
I am having similar issue. Where you able to resolve it.
I am also using the same example you were using.
I am using the following version.
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
Compatibility: 11.2.0.0.0
I do not see any notification coming back from the DB.
Appreciate your help.
Thanks & regards,
Ebe -
[PL/SQL Error] ORA-01843: not a valid month, not sure how to troubleshoot
Trying to use PL/SQL to automatically create a report that show the following:
Daily:
# of Registered Users
# of Completes (assessment) Average per User
# of Starts (assessment) Average per User
Weekly:
# of Registered Users
# of Completes (assessment) Average per User
# of Starts (assessment) Average per User
Yearly:
# of Registered Users
# of Completes (assessment) Average per User
# of Starts (assessment) Average per User
When I run the PL/SQL I get the following
[error]
ORA-01843: not a valid month
[error]
The error occurs on this part of the PL/SQL
--registered users weekly starts
select count(*), trunc(next_day(sysdate-29, 'SUNDAY')-7), trunc(sysdate-29)
into v_weekly_count_total_ru, v_weekly_start_date, v_weekly_end_date
from entities
where list_id = 3290
and participation_code_id = 10
and trunc(participation_date)
between trunc(next_day(sysdate-29, 'SUNDAY')-7) and
trunc(sysdate-29);I'm using the number 29 because I'm using a test database to test this first before moving it into production. And my test data only goes back to early August 2006.
Also, I'm not doing anything with months, so I am suprised that it is throwing this type of error.
thanksI tested a snippet of code in my production environment, just to see if I would get any results:
--registered users weekly starts
select count(*), trunc(next_day(sysdate-1, 'SUNDAY')-7), trunc(sysdate-1)
--into v_weekly_count_total_ru, v_weekly_start_date, v_weekly_end_date
from entities
where list_id = 3290
and participation_code_id = 10
and trunc(participation_date)
between trunc(next_day(sysdate-1, 'SUNDAY')-7) and trunc(sysdate-1);
COUNT(*) TRUNC(NEXT_DAY(SYSDATE-1,'SUND TRUNC(SYSDATE-1)--INTOV_WEEKLY
1 09/10/2006 00:00:00 09/11/2006 00:00:00I did a double check in my test DB to make sure there is data there:
select count(*)
from entities
where trunc(participation_date)
between to_date('01-08-2006','DD-MM-YYYY')
and to_date('14-08-2006','DD-MM-YYYY')
and list_id = 3290;
COUNT(*)
11So I'm pretty sure that I'm not pulling anything null.
thanks -
ORA-06521: PL/SQL: Error mapping function with 10.1.0 external procedure
We have an external procedure running fine on 8.1.7 on VMS. After compiling and linking succesfully under 10.1.0, I get ORA-06521 PL/SQL: Error mapping function and ORA-06522: ERROR - vms_dlsym for file x, where x in the filename of the linked executable. Another external procedure that does not connect to the 10.1.0 database runs fine. What could be causing this error in Server 10.1.0 on VMS?
Thanks,
DaveHere is the code to create the function:
CREATE OR REPLACE FUNCTION f1
(h_file_name IN VARCHAR2)
RETURN BINARY_INTEGER
IS EXTERNAL
LIBRARY l1
NAME "f1"
LANGUAGE C
WITH CONTEXT
PARAMETERS
(CONTEST,
h_file_name string);
Here is the beginning of the Pro*C:
int f1(epctx, h_file_name)
OCIExtProcContext *epctx;
char h_file_name[70];
char h_line_txt [251];
int lineno;
FILE *fptr;
/* register the connection context ... */
EXEC SQL REGISTER CONNECT USING :epctx;
The function loads a flat file into the database. It is probably not related but are unable to SQLPLUS/ or SQLLDR/ into the database from an OS autheniticated account (get ORA-12547: TNS:lost contact.) Thanks for taking the time to look at this. There aren't many people trying this on VMS, I'd bet. -
SQL 2005 Patch installation fail
Hi all
I am having error on installing KB2716429... currently the SQL server is build no. 9.0.5057
here following is the error
11/30/2013 09:46:45.484 ================================================================================
11/30/2013 09:46:45.484 Hotfix package launched
11/30/2013 09:46:45.500 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:45.500 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:45.500 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:45.500 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:45.515 Local Computer:
11/30/2013 09:46:45.515 Target Details: SV53704
11/30/2013 09:46:45.515 commonfilesdir = C:\Program Files\Common Files
11/30/2013 09:46:45.515 lcidsupportdir = e:\6ce33de16cc8ba67b3e41388bb\1033
11/30/2013 09:46:45.515 programfilesdir = C:\Program Files
11/30/2013 09:46:45.515 programfilesdir_wow = C:\Program Files
11/30/2013 09:46:45.515 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:45.515 supportdirlocal = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:45.515 windir = C:\WINDOWS
11/30/2013 09:46:45.515 winsysdir = C:\WINDOWS\system32
11/30/2013 09:46:45.515 winsysdir_wow = C:\WINDOWS\SysWOW64
11/30/2013 09:46:45.515
11/30/2013 09:46:45.531 Enumerating applicable products for this patch
11/30/2013 09:46:45.531 Found SQL 2005 product definition
11/30/2013 09:46:45.531 Warning: Product HotFixSQL is missing LCID value
11/30/2013 09:46:46.953 Enumeration: Determining QFE level for product instance MSSQLSERVER
11/30/2013 09:46:46.969 Enumeration: Found following QFE level for product instance MSSQLSERVER: 5057
11/30/2013 09:46:46.969 Enumeration: Determining GDR branching Hotfix for product instance MSSQLSERVER
11/30/2013 09:46:46.969 Enumeration: Found following GDR branch hotfix for product instance MSSQLSERVER: 5292
11/30/2013 09:46:46.969 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:46.984 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:46.984 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:46.984 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:46.984 Product discovery completed during the install process for MSSQLSERVER
11/30/2013 09:46:46.984 SP Level check completed during the install process for MSSQLSERVER
11/30/2013 09:46:46.984 Product language check completed during the install process for MSSQLSERVER
11/30/2013 09:46:46.984 Product version check completed during the install process for MSSQLSERVER
11/30/2013 09:46:46.984 Command-line instance name check completed during the install process
11/30/2013 09:46:46.984 Baseline build check completed during the installation process for MSSQLSERVER
11/30/2013 09:46:47.000 Baseline build check completed during the install process
11/30/2013 09:46:47.000 Found OLAP Server 2005 product definition
11/30/2013 09:46:47.000 Warning: Product HotFixAS is missing LCID value
11/30/2013 09:46:48.453 Enumeration: Determining QFE level for product instance MSSQLSERVER
11/30/2013 09:46:48.453 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\\Bin\msmdsrv.exe
11/30/2013 09:46:48.453 Enumeration: Found following QFE level for product instance MSSQLSERVER: 5057
11/30/2013 09:46:48.453 Enumeration: Determining GDR branching Hotfix for product instance MSSQLSERVER
11/30/2013 09:46:48.453 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\\Bin\msmdsrv.exe
11/30/2013 09:46:48.453 Enumeration: No GDR branch Hotfix found for product instance MSSQLSERVER
11/30/2013 09:46:48.469 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:48.469 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:48.469 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:48.469 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:48.469 Product discovery completed during the install process for MSSQLSERVER
11/30/2013 09:46:48.469 SP Level check completed during the install process for MSSQLSERVER
11/30/2013 09:46:48.469 Product language check completed during the install process for MSSQLSERVER
11/30/2013 09:46:48.484 Product version check completed during the install process for MSSQLSERVER
11/30/2013 09:46:48.484 Command-line instance name check completed during the install process
11/30/2013 09:46:48.484 Baseline build check completed during the installation process for MSSQLSERVER
11/30/2013 09:46:48.484 Baseline build check completed during the install process
11/30/2013 09:46:48.484 Found Notification Services 2005 product definition
11/30/2013 09:46:48.484 Warning: Product HotFixNS is missing LCID value
11/30/2013 09:46:50.015 Enumeration: Determining QFE level for product instance
11/30/2013 09:46:50.047 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\90\NotificationServices\9.0.242\\Bin\nsservice.exe
11/30/2013 09:46:50.062 Enumeration: Found following QFE level for product instance : 5057
11/30/2013 09:46:50.062 Enumeration: Determining GDR branching Hotfix for product instance
11/30/2013 09:46:50.062 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\90\NotificationServices\9.0.242\\Bin\nsservice.exe
11/30/2013 09:46:50.062 Enumeration: Found following GDR branch hotfix for product instance : 5292
11/30/2013 09:46:50.062 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:50.062 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:50.062 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:50.078 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:50.078 Product discovery completed during the install process for NS
11/30/2013 09:46:50.078 SP Level check completed during the install process for NS
11/30/2013 09:46:50.078 Product language check completed during the install process for NS
11/30/2013 09:46:50.078 Product version check completed during the install process for NS
11/30/2013 09:46:50.078 Baseline build check completed during the installation process for NS
11/30/2013 09:46:50.078 Baseline build check completed during the install process
11/30/2013 09:46:50.078 Found Report Server 2005 product definition
11/30/2013 09:46:50.109 Warning: Product HotFixRS is missing LCID value
11/30/2013 09:46:51.687 Enumeration: Determining QFE level for product instance MSSQLSERVER
11/30/2013 09:46:51.703 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\\ReportServer\bin\ReportingServicesService.exe
11/30/2013 09:46:51.703 Enumeration: Found following QFE level for product instance MSSQLSERVER: 5057
11/30/2013 09:46:51.703 Enumeration: Determining GDR branching Hotfix for product instance MSSQLSERVER
11/30/2013 09:46:51.703 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\\ReportServer\bin\ReportingServicesService.exe
11/30/2013 09:46:51.703 Enumeration: Found following GDR branch hotfix for product instance MSSQLSERVER: 5292
11/30/2013 09:46:51.703 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:51.703 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:51.703 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:51.703 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:51.703 Product discovery completed during the install process for MSSQLSERVER
11/30/2013 09:46:51.703 SP Level check completed during the install process for MSSQLSERVER
11/30/2013 09:46:51.703 Product language check completed during the install process for MSSQLSERVER
11/30/2013 09:46:51.703 Product version check completed during the install process for MSSQLSERVER
11/30/2013 09:46:51.719 Command-line instance name check completed during the install process
11/30/2013 09:46:51.750 Baseline build check completed during the installation process for MSSQLSERVER
11/30/2013 09:46:51.750 Baseline build check completed during the install process
11/30/2013 09:46:51.765 Found DTS 2005 product definition
11/30/2013 09:46:51.765 Warning: Product HotFixDTS is missing LCID value
11/30/2013 09:46:53.359 Enumeration: Determining QFE level for product instance
11/30/2013 09:46:53.375 Enumeration: Found following QFE level for product instance : 5057
11/30/2013 09:46:53.375 Enumeration: Determining GDR branching Hotfix for product instance
11/30/2013 09:46:53.375 Enumeration: Found following GDR branch hotfix for product instance : 5292
11/30/2013 09:46:53.375 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:53.375 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:53.375 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:53.375 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:53.375 Product discovery completed during the install process for Integration Services
11/30/2013 09:46:53.375 SP Level check completed during the install process for Integration Services
11/30/2013 09:46:53.375 Product language check completed during the install process for Integration Services
11/30/2013 09:46:53.375 Product version check completed during the install process for Integration Services
11/30/2013 09:46:53.375 Baseline build check completed during the installation process for Integration Services
11/30/2013 09:46:53.375 Baseline build check completed during the install process
11/30/2013 09:46:53.390 Found SQL 2005 Tools product definition
11/30/2013 09:46:53.390 Warning: Product HotFixTools is missing LCID value
11/30/2013 09:46:54.953 Enumeration: Determining GDR branching Hotfix for product instance
11/30/2013 09:46:54.969 Enumeration: Found following GDR branch hotfix for product instance : 5292
11/30/2013 09:46:54.969 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:54.969 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:54.969 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:54.969 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:54.969 Product discovery completed during the install process for SQL Tools
11/30/2013 09:46:54.969 SP Level check completed during the install process for SQL Tools
11/30/2013 09:46:54.969 Product language check completed during the install process for SQL Tools
11/30/2013 09:46:54.984 Product version check completed during the install process for SQL Tools
11/30/2013 09:46:54.984 Baseline build check completed during the installation process for SQL Tools
11/30/2013 09:46:54.984 Baseline build check completed during the install process
11/30/2013 09:46:55.031 Product Enumeration Results:
11/30/2013 09:46:55.031 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixSQL.inf
11/30/2013 09:46:55.031 arpfolder = SQL9_KB2716429_ENU
11/30/2013 09:46:55.031 associatedhotfixbuild = 5320
11/30/2013 09:46:55.031 baselinebuild = 5000
11/30/2013 09:46:55.031 baselinebuildmax = 5069
11/30/2013 09:46:55.031 build = 5069
11/30/2013 09:46:55.031 description = SQL Server Database Services 2005
11/30/2013 09:46:55.031 details = Patch for SQL Server Database Services 2005
11/30/2013 09:46:55.031 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.031 kbarticle = KB2716429
11/30/2013 09:46:55.031 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.031 legalproductname = SQL Server Database Services 2005
11/30/2013 09:46:55.031 machinetype = x86
11/30/2013 09:46:55.031 package = HotFixSQL
11/30/2013 09:46:55.031 packagetype = GDR
11/30/2013 09:46:55.031 productname = SQL9
11/30/2013 09:46:55.047 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.047 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.047 splevel = 4
11/30/2013 09:46:55.047 sqlutility = sqlcmd.exe
11/30/2013 09:46:55.047 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.047 version = 9
11/30/2013 09:46:55.047
11/30/2013 09:46:55.047 File Group Details: MSP
11/30/2013 09:46:55.047 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.047 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.047 File Details: sqlrun_sql.msp
11/30/2013 09:46:55.047
11/30/2013 09:46:55.047 Instance Details: MSSQLSERVER
11/30/2013 09:46:55.047 agentservicename = SQLSERVERAGENT
11/30/2013 09:46:55.047 associatedhotfixbuild = 5292
11/30/2013 09:46:55.047 clustername =
11/30/2013 09:46:55.047 default = TRUE
11/30/2013 09:46:55.047 ftsservicename = MSFTESQL
11/30/2013 09:46:55.047 fullversion = 2005.090.5057.00
11/30/2013 09:46:55.047 hiveregpath = Software\Microsoft\Microsoft SQL Server\MSSQL.1
11/30/2013 09:46:55.047 id = MSSQL.1
11/30/2013 09:46:55.062 installsqldatadir = C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL
11/30/2013 09:46:55.062 installsqldir = C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL
11/30/2013 09:46:55.062 lcid = 1033
11/30/2013 09:46:55.062 name = MSSQLSERVER
11/30/2013 09:46:55.062 productcode = {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
11/30/2013 09:46:55.062 qfelevel = 5057
11/30/2013 09:46:55.062 servicename = MSSQLServer
11/30/2013 09:46:55.062 sku = STANDARD
11/30/2013 09:46:55.062 sp = 4
11/30/2013 09:46:55.094 type = SQL Server Standalone Product
11/30/2013 09:46:55.094 vermajbld = 5000
11/30/2013 09:46:55.094 version = 9
11/30/2013 09:46:55.109
11/30/2013 09:46:55.125 Product Enumeration Results:
11/30/2013 09:46:55.140 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixAS.inf
11/30/2013 09:46:55.140 arpfolder = OLAP9_KB2716429_ENU
11/30/2013 09:46:55.140 associatedhotfixbuild = 5320
11/30/2013 09:46:55.140 baselinebuild = 5000
11/30/2013 09:46:55.140 baselinebuildmax = 5069
11/30/2013 09:46:55.140 build = 5069
11/30/2013 09:46:55.140 description = SQL Server Analysis Services 2005
11/30/2013 09:46:55.140 details = Patch for Analysis Services 2005
11/30/2013 09:46:55.140 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.140 kbarticle = KB2716429
11/30/2013 09:46:55.140 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.140 legalproductname = SQL Server Analysis Services 2005
11/30/2013 09:46:55.156 machinetype = x86
11/30/2013 09:46:55.156 package = HotFixAS
11/30/2013 09:46:55.156 packagetype = GDR
11/30/2013 09:46:55.156 productname = OLAP9
11/30/2013 09:46:55.156 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.156 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.156 splevel = 4
11/30/2013 09:46:55.156 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.156 validateauthentication = true
11/30/2013 09:46:55.156 version = 9
11/30/2013 09:46:55.156
11/30/2013 09:46:55.156 File Group Details: MSP
11/30/2013 09:46:55.156 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.156 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.172 File Details: sqlrun_as.msp
11/30/2013 09:46:55.172
11/30/2013 09:46:55.172 Instance Details: MSSQLSERVER
11/30/2013 09:46:55.172 associatedhotfixbuild = 1520
11/30/2013 09:46:55.172 clustername =
11/30/2013 09:46:55.187 default = TRUE
11/30/2013 09:46:55.203 fullversion = 2005.090.5057.00
11/30/2013 09:46:55.219 hiveregpath = Software\Microsoft\Microsoft SQL Server\MSSQL.2
11/30/2013 09:46:55.219 id = MSSQL.2
11/30/2013 09:46:55.219 installsqldatadir = C:\Program Files\Microsoft SQL Server\
11/30/2013 09:46:55.234 installsqldir = C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\
11/30/2013 09:46:55.250 lcid = 1033
11/30/2013 09:46:55.265 name = MSSQLSERVER
11/30/2013 09:46:55.297 olapservicename = MSSQLServerOLAPService
11/30/2013 09:46:55.297 productcode = {8ABF8FEB-ABB0-40DC-9945-85AF36EF30A9}
11/30/2013 09:46:55.297 qfelevel = 5057
11/30/2013 09:46:55.297 servicename = MSSQLServerOLAPService
11/30/2013 09:46:55.297 sku = STANDARD
11/30/2013 09:46:55.297 sp = 4
11/30/2013 09:46:55.297 type = Olap Standalone Product
11/30/2013 09:46:55.297 vermajbld = 5000
11/30/2013 09:46:55.297 version = 9
11/30/2013 09:46:55.297
11/30/2013 09:46:55.297 Product Enumeration Results:
11/30/2013 09:46:55.297 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixNS.inf
11/30/2013 09:46:55.297 arpfolder = NS9_KB2716429_ENU
11/30/2013 09:46:55.297 associatedhotfixbuild = 5320
11/30/2013 09:46:55.297 baselinebuild = 5000
11/30/2013 09:46:55.297 baselinebuildmax = 5069
11/30/2013 09:46:55.297 build = 5069
11/30/2013 09:46:55.297 description = SQL Server Notification Services 2005
11/30/2013 09:46:55.297 details = Patch for SQL Server Notification Services 2005
11/30/2013 09:46:55.297 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.312 kbarticle = KB2716429
11/30/2013 09:46:55.312 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.312 legalproductname = SQL Server Notification Services 2005 instances
11/30/2013 09:46:55.312 machinetype = x86
11/30/2013 09:46:55.312 package = HotFixNS
11/30/2013 09:46:55.312 packagetype = GDR
11/30/2013 09:46:55.312 productname = NS9
11/30/2013 09:46:55.312 recommendinstall = 1
11/30/2013 09:46:55.312 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.312 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.312 splevel = 4
11/30/2013 09:46:55.312 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.312 validateauthentication = true
11/30/2013 09:46:55.312 version = 9
11/30/2013 09:46:55.312
11/30/2013 09:46:55.312 File Group Details: MSP
11/30/2013 09:46:55.312 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.312 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.312 File Details: sqlrun_ns.msp
11/30/2013 09:46:55.312
11/30/2013 09:46:55.312 Instance Details: NS
11/30/2013 09:46:55.312 associatedhotfixbuild = 5292
11/30/2013 09:46:55.328 clustername =
11/30/2013 09:46:55.328 fullversion = 9.00.5057.00
11/30/2013 09:46:55.328 hiveregpath = Software\Microsoft\Microsoft SQL Server\90\NS
11/30/2013 09:46:55.328 id =
11/30/2013 09:46:55.328 installsqldatadir =
11/30/2013 09:46:55.328 installsqldir = C:\Program Files\Microsoft SQL Server\90\NotificationServices\9.0.242\
11/30/2013 09:46:55.328 lcid = 1033
11/30/2013 09:46:55.328 name =
11/30/2013 09:46:55.375 productcode = {37E9AD9F-3217-4229-B5A5-7A0C82364C6C}
11/30/2013 09:46:55.390 qfelevel = 5057
11/30/2013 09:46:55.406 sku = STANDARD
11/30/2013 09:46:55.406 sp = 4
11/30/2013 09:46:55.406 type = Tools Only
11/30/2013 09:46:55.406 vermajbld = 5000
11/30/2013 09:46:55.422 version = 9
11/30/2013 09:46:55.422
11/30/2013 09:46:55.422 Product Enumeration Results:
11/30/2013 09:46:55.422 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixRS.inf
11/30/2013 09:46:55.422 arpfolder = RS9_KB2716429_ENU
11/30/2013 09:46:55.422 associatedhotfixbuild = 5320
11/30/2013 09:46:55.422 baselinebuild = 5000
11/30/2013 09:46:55.422 baselinebuildmax = 5069
11/30/2013 09:46:55.422 build = 5069
11/30/2013 09:46:55.453 description = SQL Server Reporting Services 2005
11/30/2013 09:46:55.453 details = Patch for SQL Server Reporting Services 2005
11/30/2013 09:46:55.453 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.453 kbarticle = KB2716429
11/30/2013 09:46:55.453 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.453 legalproductname = SQL Server Reporting Services 2005
11/30/2013 09:46:55.453 machinetype = x86
11/30/2013 09:46:55.453 package = HotFixRS
11/30/2013 09:46:55.453 packagetype = GDR
11/30/2013 09:46:55.453 productname = RS9
11/30/2013 09:46:55.469 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.469 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.469 splevel = 4
11/30/2013 09:46:55.469 sqlutility = sqlcmd.exe
11/30/2013 09:46:55.469 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.469 validateauthentication = true
11/30/2013 09:46:55.469 version = 9
11/30/2013 09:46:55.469
11/30/2013 09:46:55.469 File Group Details: MSP
11/30/2013 09:46:55.469 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.469 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.469 File Details: sqlrun_rs.msp
11/30/2013 09:46:55.469
11/30/2013 09:46:55.469 Instance Details: MSSQLSERVER
11/30/2013 09:46:55.469 associatedhotfixbuild = 5292
11/30/2013 09:46:55.469 clustername =
11/30/2013 09:46:55.469 default = TRUE
11/30/2013 09:46:55.469 fullversion = 9.00.5057.00
11/30/2013 09:46:55.469 hiveregpath = Software\Microsoft\Microsoft SQL Server\MSSQL.3
11/30/2013 09:46:55.469 id = MSSQL.3
11/30/2013 09:46:55.469 installsqldatadir =
11/30/2013 09:46:55.469 installsqldir = C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\
11/30/2013 09:46:55.484 lcid = 1033
11/30/2013 09:46:55.484 name = MSSQLSERVER
11/30/2013 09:46:55.484 productcode = {E930E839-998E-42F9-97E2-71FC960DB1B7}
11/30/2013 09:46:55.484 qfelevel = 5057
11/30/2013 09:46:55.484 rsservicename = ReportServer
11/30/2013 09:46:55.484 servicename =
11/30/2013 09:46:55.484 sku = STANDARD
11/30/2013 09:46:55.484 sp = 4
11/30/2013 09:46:55.484 type = Report Server Standalone Product
11/30/2013 09:46:55.484 vermajbld = 5000
11/30/2013 09:46:55.484 version = 9
11/30/2013 09:46:55.484
11/30/2013 09:46:55.484 Product Enumeration Results:
11/30/2013 09:46:55.484 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixDTS.inf
11/30/2013 09:46:55.500 arpfolder = DTS9_KB2716429_ENU
11/30/2013 09:46:55.625 associatedhotfixbuild = 5320
11/30/2013 09:46:55.625 baselinebuild = 5000
11/30/2013 09:46:55.625 baselinebuildmax = 5069
11/30/2013 09:46:55.625 build = 5069
11/30/2013 09:46:55.625 description = SQL Server Integration Services 2005
11/30/2013 09:46:55.625 details = Patch for SQL Server Integration Services 2005
11/30/2013 09:46:55.625 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.625 kbarticle = KB2716429
11/30/2013 09:46:55.625 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.625 legalproductname = SQL Server Integration Services 2005
11/30/2013 09:46:55.625 machinetype = x86
11/30/2013 09:46:55.640 package = HotFixDTS
11/30/2013 09:46:55.640 packagetype = GDR
11/30/2013 09:46:55.640 productname = DTS9
11/30/2013 09:46:55.640 recommendinstall = 1
11/30/2013 09:46:55.640 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.640 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.640 splevel = 4
11/30/2013 09:46:55.640 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.640 version = 9
11/30/2013 09:46:55.640
11/30/2013 09:46:55.640 File Group Details: MSP
11/30/2013 09:46:55.640 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.640 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.640 File Details: sqlrun_dts.msp
11/30/2013 09:46:55.640
11/30/2013 09:46:55.640 Instance Details: Integration Services
11/30/2013 09:46:55.640 associatedhotfixbuild = 5292
11/30/2013 09:46:55.640 clustername =
11/30/2013 09:46:55.640 dtsservicename = MsDtsServer
11/30/2013 09:46:55.640 fullversion = 9.00.5057.00
11/30/2013 09:46:55.656 hiveregpath = Software\Microsoft\Microsoft SQL Server\90\DTS
11/30/2013 09:46:55.656 id =
11/30/2013 09:46:55.656 installsqldatadir =
11/30/2013 09:46:55.656 installsqldir = C:\Program Files\Microsoft SQL Server\90\DTS\
11/30/2013 09:46:55.656 lcid = 1033
11/30/2013 09:46:55.656 name =
11/30/2013 09:46:55.656 productcode = {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
11/30/2013 09:46:55.656 qfelevel = 5057
11/30/2013 09:46:55.656 servicename = MsDtsServer
11/30/2013 09:46:55.656 sku = STANDARD
11/30/2013 09:46:55.656 sp = 4
11/30/2013 09:46:55.656 type = Tools Only
11/30/2013 09:46:55.656 vermajbld = 5000
11/30/2013 09:46:55.656 version = 9
11/30/2013 09:46:55.656
11/30/2013 09:46:55.656 Product Enumeration Results:
11/30/2013 09:46:55.672 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixTools.inf
11/30/2013 09:46:55.672 arpfolder = SQLTools9_KB2716429_ENU
11/30/2013 09:46:55.672 associatedhotfixbuild = 5320
11/30/2013 09:46:55.672 baselinebuild = 5000
11/30/2013 09:46:55.672 baselinebuildmax = 5069
11/30/2013 09:46:55.672 build = 5069
11/30/2013 09:46:55.672 description = SQL Server Tools and Workstation Components 2005
11/30/2013 09:46:55.672 details = Patch for SQL Server Tools and Workstation Components 2005
11/30/2013 09:46:55.672 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.672 kbarticle = KB2716429
11/30/2013 09:46:55.672 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.672 legalproductname = SQL Server Tools and Workstation Components 2005
11/30/2013 09:46:55.672 machinetype = x86
11/30/2013 09:46:55.672 package = HotFixTools
11/30/2013 09:46:55.672 packagetype = GDR
11/30/2013 09:46:55.672 productname = SQLTools9
11/30/2013 09:46:55.672 recommendinstall = 1
11/30/2013 09:46:55.672 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.672 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.672 splevel = 4
11/30/2013 09:46:55.672 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.687 version = 9
11/30/2013 09:46:55.687
11/30/2013 09:46:55.687 File Group Details: MSP
11/30/2013 09:46:55.687 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.687 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.687 File Details: sqlrun_tools.msp
11/30/2013 09:46:55.687
11/30/2013 09:46:55.687 Instance Details: SQL Tools
11/30/2013 09:46:55.687 associatedhotfixbuild = 5292
11/30/2013 09:46:55.687 clustername =
11/30/2013 09:46:55.687 fullversion = 9.4.5057
11/30/2013 09:46:55.687 hiveregpath = Software\Microsoft\Microsoft SQL Server\90\Tools
11/30/2013 09:46:55.687 id =
11/30/2013 09:46:55.687 installsqldatadir =
11/30/2013 09:46:55.687 installsqldir = C:\Program Files\Microsoft SQL Server\90\Tools\
11/30/2013 09:46:55.687 lcid = 1033
11/30/2013 09:46:55.687 name =
11/30/2013 09:46:55.687 productcode = {1DD463C0-A50A-4394-B7E4-5895C02F9E0D}
11/30/2013 09:46:55.687 qfelevel = 5057
11/30/2013 09:46:55.687 sku = STANDARD
11/30/2013 09:46:55.687 sp = 4
11/30/2013 09:46:55.687 type = Tools Only
11/30/2013 09:46:55.703 vermajbld = 5000
11/30/2013 09:46:55.703 version = 9
11/30/2013 09:46:55.703
11/30/2013 09:47:00.781 Registry: Opened registry key "System\CurrentControlSet\Control\Session Manager"
11/30/2013 09:47:00.781 Registry: Cannot read registry key value "PendingFileRenameOperations", error 0
11/30/2013 09:47:00.812 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:01.719 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:01.734 Locked file: Checking for locked files
11/30/2013 09:47:04.328 Attempting to pause the 32 bit ngen queue
11/30/2013 09:47:04.968 Installing product: SQL9
11/30/2013 09:47:05.781 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:05.781 Installing instance: MSSQLSERVER
11/30/2013 09:47:05.812 Installing target: SV53704
11/30/2013 09:47:05.828 Installing file: sqlrun_sql.msp
11/30/2013 09:47:05.828 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2716429_sqlrun_sql.msp.log
11/30/2013 09:47:05.828 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:05.828 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:06.203 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:06.203 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:06.203 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:06.218 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixSQL\Files\sqlrun_sql.msp
11/30/2013 09:47:06.218 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:06.218 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:06.640 Watson: Param1 = Unknown
11/30/2013 09:47:06.640 Watson: Param2 = 0x66e
11/30/2013 09:47:06.640 Watson: Param3 = Unknown
11/30/2013 09:47:06.640 Watson: Param4 = 0x66e
11/30/2013 09:47:06.656 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:06.656 Watson: Param6 = Unknown
11/30/2013 09:47:06.656 Watson: Param7 = SQL9
11/30/2013 09:47:06.656 Watson: Param8 = @
11/30/2013 09:47:06.656 Watson: Param9 = x86
11/30/2013 09:47:06.656 Watson: Param10 = 5069
11/30/2013 09:47:06.656 Installed product: SQL9
11/30/2013 09:47:06.656 Installing product: OLAP9
11/30/2013 09:47:07.468 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:07.484 Installing instance: MSSQLSERVER
11/30/2013 09:47:07.484 Installing target: SV53704
11/30/2013 09:47:07.500 Installing file: sqlrun_as.msp
11/30/2013 09:47:07.500 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\OLAP9_Hotfix_KB2716429_sqlrun_as.msp.log
11/30/2013 09:47:07.515 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:07.515 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:07.640 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:07.640 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:07.640 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:07.656 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixAS\Files\sqlrun_as.msp
11/30/2013 09:47:07.656 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:07.656 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:08.078 Watson: Param1 = Unknown
11/30/2013 09:47:08.078 Watson: Param2 = 0x66e
11/30/2013 09:47:08.078 Watson: Param3 = Unknown
11/30/2013 09:47:08.078 Watson: Param4 = 0x66e
11/30/2013 09:47:08.078 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:08.078 Watson: Param6 = Unknown
11/30/2013 09:47:08.078 Watson: Param7 = OLAP9
11/30/2013 09:47:08.078 Watson: Param8 = @
11/30/2013 09:47:08.078 Watson: Param9 = x86
11/30/2013 09:47:08.078 Watson: Param10 = 5069
11/30/2013 09:47:08.078 Installed product: OLAP9
11/30/2013 09:47:08.078 Installing product: RS9
11/30/2013 09:47:08.875 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:08.875 Installing instance: MSSQLSERVER
11/30/2013 09:47:08.890 Installing target: SV53704
11/30/2013 09:47:08.890 Installing file: sqlrun_rs.msp
11/30/2013 09:47:08.890 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\RS9_Hotfix_KB2716429_sqlrun_rs.msp.log
11/30/2013 09:47:08.890 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:08.890 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:09.015 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:09.015 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:09.015 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:09.031 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixRS\Files\sqlrun_rs.msp
11/30/2013 09:47:09.047 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:09.047 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:09.593 Watson: Param1 = Unknown
11/30/2013 09:47:09.593 Watson: Param2 = 0x66e
11/30/2013 09:47:09.593 Watson: Param3 = Unknown
11/30/2013 09:47:09.609 Watson: Param4 = 0x66e
11/30/2013 09:47:09.609 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:09.609 Watson: Param6 = Unknown
11/30/2013 09:47:09.609 Watson: Param7 = RS9
11/30/2013 09:47:09.609 Watson: Param8 = @
11/30/2013 09:47:09.609 Watson: Param9 = x86
11/30/2013 09:47:09.609 Watson: Param10 = 5069
11/30/2013 09:47:09.625 Installed product: RS9
11/30/2013 09:47:09.625 Installing product: NS9
11/30/2013 09:47:10.406 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:10.406 Installing instance: NS
11/30/2013 09:47:10.422 Installing target: SV53704
11/30/2013 09:47:10.422 Installing file: sqlrun_ns.msp
11/30/2013 09:47:10.422 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\NS9_Hotfix_KB2716429_sqlrun_ns.msp.log
11/30/2013 09:47:10.422 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:10.422 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:10.531 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:10.531 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:10.531 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:10.547 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixNS\Files\sqlrun_ns.msp
11/30/2013 09:47:10.547 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:10.547 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:10.890 Watson: Param1 = Unknown
11/30/2013 09:47:10.890 Watson: Param2 = 0x66e
11/30/2013 09:47:10.890 Watson: Param3 = Unknown
11/30/2013 09:47:10.890 Watson: Param4 = 0x66e
11/30/2013 09:47:10.890 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:10.890 Watson: Param6 = Unknown
11/30/2013 09:47:10.890 Watson: Param7 = NS9
11/30/2013 09:47:10.890 Watson: Param8 = @
11/30/2013 09:47:10.890 Watson: Param9 = x86
11/30/2013 09:47:10.890 Watson: Param10 = 5069
11/30/2013 09:47:10.890 Installed product: NS9
11/30/2013 09:47:10.890 Installing product: DTS9
11/30/2013 09:47:11.703 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:11.703 Installing instance: Integration Services
11/30/2013 09:47:11.703 Installing target: SV53704
11/30/2013 09:47:11.703 Installing file: sqlrun_dts.msp
11/30/2013 09:47:11.703 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB2716429_sqlrun_dts.msp.log
11/30/2013 09:47:11.703 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:11.718 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:11.890 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:11.890 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:11.906 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:11.906 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixDTS\Files\sqlrun_dts.msp
11/30/2013 09:47:11.922 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:11.922 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:12.328 Watson: Param1 = Unknown
11/30/2013 09:47:12.328 Watson: Param2 = 0x66e
11/30/2013 09:47:12.328 Watson: Param3 = Unknown
11/30/2013 09:47:12.328 Watson: Param4 = 0x66e
11/30/2013 09:47:12.328 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:12.328 Watson: Param6 = Unknown
11/30/2013 09:47:12.328 Watson: Param7 = DTS9
11/30/2013 09:47:12.328 Watson: Param8 = @
11/30/2013 09:47:12.328 Watson: Param9 = x86
11/30/2013 09:47:12.328 Watson: Param10 = 5069
11/30/2013 09:47:12.343 Installed product: DTS9
11/30/2013 09:47:12.343 Installing product: SQLTools9
11/30/2013 09:47:13.125 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:13.140 Installing instance: SQL Tools
11/30/2013 09:47:13.140 Installing target: SV53704
11/30/2013 09:47:13.156 Installing file: sqlrun_tools.msp
11/30/2013 09:47:13.172 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB2716429_sqlrun_tools.msp.log
11/30/2013 09:47:13.172 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:13.172 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:13.484 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:13.484 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:13.484 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:13.500 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixTools\Files\sqlrun_tools.msp
11/30/2013 09:47:13.500 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:13.500 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:13.828 Watson: Param1 = Unknown
11/30/2013 09:47:13.828 Watson: Param2 = 0x66e
11/30/2013 09:47:13.843 Watson: Param3 = Unknown
11/30/2013 09:47:13.843 Watson: Param4 = 0x66e
11/30/2013 09:47:13.843 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:13.843 Watson: Param6 = Unknown
11/30/2013 09:47:13.843 Watson: Param7 = SQLTools9
11/30/2013 09:47:13.843 Watson: Param8 = @
11/30/2013 09:47:13.843 Watson: Param9 = x86
11/30/2013 09:47:13.843 Watson: Param10 = 5069
11/30/2013 09:47:13.843 Installed product: SQLTools9
11/30/2013 09:47:13.843 Hotfix package completed
11/30/2013 09:47:13.859 Attempting to continue the 32 bit ngen queueHi ~ any idea on this case ? here is the one MSP installation log:
=== Verbose logging started: 11/30/2013 21:28:15 Build type: SHIP UNICODE 4.05.6001.00 Calling process: e:\de60d5388bc787220900e629b152c9\hotfix.exe ===
MSI (c) (D4:28) [21:28:15:681]: Resetting cached policy values
MSI (c) (D4:28) [21:28:15:681]: Machine policy value 'Debug' is 0
MSI (c) (D4:28) [21:28:15:681]: ******* RunEngine:
******* Product: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
******* Action:
******* CommandLine: **********
MSI (c) (D4:28) [21:28:15:681]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (D4:28) [21:28:15:681]: Grabbed execution mutex.
MSI (c) (D4:28) [21:28:15:697]: Cloaking enabled.
MSI (c) (D4:28) [21:28:15:697]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (D4:28) [21:28:15:697]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (A8:C0) [21:28:15:697]: Running installation inside multi-package transaction {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
MSI (s) (A8:C0) [21:28:15:697]: Grabbed execution mutex.
MSI (s) (A8:04) [21:28:15:697]: Resetting cached policy values
MSI (s) (A8:04) [21:28:15:697]: Machine policy value 'Debug' is 0
MSI (s) (A8:04) [21:28:15:697]: ******* RunEngine:
******* Product: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
******* Action:
******* CommandLine: **********
MSI (s) (A8:04) [21:28:15:697]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (A8:04) [21:28:15:931]: End dialog not enabled
MSI (s) (A8:04) [21:28:15:931]: Original package ==> C:\WINDOWS\Installer\181c1.msi
MSI (s) (A8:04) [21:28:15:931]: Package we're running from ==> C:\WINDOWS\Installer\181c1.msi
MSI (s) (A8:04) [21:28:15:994]: APPCOMPAT: looking for appcompat database entry with ProductCode '{EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}'.
MSI (s) (A8:04) [21:28:15:994]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (A8:04) [21:28:15:994]: Opening existing patch 'C:\WINDOWS\Installer\e9ff36e.msp'.
MSI (s) (A8:04) [21:28:16:010]: Opening existing patch 'C:\WINDOWS\Installer\239697ae.msp'.
MSI (s) (A8:04) [21:28:16:056]: File will have security applied from OpCode.
MSI (s) (A8:04) [21:28:16:056]: Original patch ==> e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp
MSI (s) (A8:04) [21:28:16:056]: Patch we're running from ==> C:\WINDOWS\Installer\1f80a9f.msp
MSI (s) (A8:04) [21:28:16:072]: SOFTWARE RESTRICTION POLICY: Verifying patch --> 'e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp' against software restriction policy
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (s) (A8:04) [21:28:16:072]: SOFTWARE RESTRICTION POLICY: e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp is not digitally signed
MSI (s) (A8:04) [21:28:16:072]: SOFTWARE RESTRICTION POLICY: e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp is permitted to run at the 'unrestricted' authorization level.
MSI (s) (A8:04) [21:28:16:072]: SequencePatches starts. Product code: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}, Product version: 9.00.1399.06, Upgrade code: {2B33A057-4470-45CD-8E63-863CB78FC626}, Product language 1033
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: _Tables 3: -2147287038
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: _Columns 3: -2147287038
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: _Tables 3: -2147287038
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: _Columns 3: -2147287038
MSI (s) (A8:04) [21:28:16:072]: PATCH SEQUENCER: verifying the applicability of QFE patch e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp against product code: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}, product version: 9.00.1399.06, product language
1033 and upgrade code: {2B33A057-4470-45CD-8E63-863CB78FC626}
MSI (s) (A8:04) [21:28:16:072]: PATCH SEQUENCER: QFE patch e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp is not applicable.
MSI (s) (A8:04) [21:28:16:072]: SequencePatches returns success.
MSI (s) (A8:04) [21:28:16:072]: Final Patch Application Order:
MSI (s) (A8:04) [21:28:16:072]: Other Patches:
MSI (s) (A8:04) [21:28:16:072]: Unknown\Absent: {4C3BC5C8-67A5-40F1-85B7-D9341A5F7B6C} - e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp
MSI (s) (A8:04) [21:28:16:072]: Superseded: {5E9ADA2D-3132-42CF-8628-D2ADA0F335EE} -
MSI (s) (A8:04) [21:28:16:072]: Superseded: {32BCE9F2-8686-487A-80A9-A401C0F7DCBD} -
MSI (s) (A8:04) [21:28:16:072]: Unknown\Absent: {D23D25E7-0AB4-41EE-81B5-F0CF34D1BA2B} -
MSI (s) (A8:04) [21:28:16:072]: Unknown\Absent: {CF321155-04AA-4CF8-BB9A-DA3144835E3E} -
MSI (s) (A8:04) [21:28:16:072]: Machine policy value 'DisablePatch' is 0
MSI (s) (A8:04) [21:28:16:072]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (A8:04) [21:28:16:072]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (A8:04) [21:28:16:072]: Disallowing uninstallation of patch {CF321155-04AA-4CF8-BB9A-DA3144835E3E} because the patch is marked as not uninstallable
MSI (s) (A8:04) [21:28:16:072]: Product: Microsoft SQL Server 2005 Integration Services - Update 'Service Pack 4 for SQL Server Integration Services 2005 ENU (KB2463332)' could not be removed. Error code 1646. Additional information is available in the log
file C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB2716429_sqlrun_dts.msp.log.
MSI (s) (A8:04) [21:28:16:072]: Windows Installer removed an update. Product Name: Microsoft SQL Server 2005 Integration Services. Product Version: 9.00.1399.06. Product Language: 1033. Update Name: Service Pack 4 for SQL Server Integration Services 2005 ENU
(KB2463332). Removal success or error status: 0.
MSI (s) (A8:04) [21:28:16:072]: Product: Microsoft SQL Server 2005 Integration Services - Update '{4C3BC5C8-67A5-40F1-85B7-D9341A5F7B6C}' could not be installed. Error code 1646. Additional information is available in the log file C:\Program Files\Microsoft
SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB2716429_sqlrun_dts.msp.log.
MSI (s) (A8:04) [21:28:16:072]: Windows Installer installed an update. Product Name: Microsoft SQL Server 2005 Integration Services. Product Version: 9.00.1399.06. Product Language: 1033. Update Name: {4C3BC5C8-67A5-40F1-85B7-D9341A5F7B6C}. Installation success
or error status: 1646.
MSI (s) (A8:04) [21:28:16:072]: Product: Microsoft SQL Server 2005 Integration Services - Update 'GDR 5057 for SQL Server Integration Services 2005 ENU (KB2494120)' could not be removed. Error code 1646. Additional information is available in the log file C:\Program
Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB2716429_sqlrun_dts.msp.log.
MSI (s) (A8:04) [21:28:16:072]: Windows Installer removed an update. Product Name: Microsoft SQL Server 2005 Integration Services. Product Version: 9.00.1399.06. Product Language: 1033. Update Name: GDR 5057 for SQL Server Integration Services 2005 ENU (KB2494120).
Removal success or error status: 1646.
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 1708
MSI (s) (A8:04) [21:28:16:072]: Product: Microsoft SQL Server 2005 Integration Services -- Installation failed.
MSI (s) (A8:04) [21:28:16:072]: Windows Installer installed the product. Product Name: Microsoft SQL Server 2005 Integration Services. Product Version: 9.00.1399.06. Product Language: 1033. Installation success or error status: 1646.
MSI (s) (A8:04) [21:28:16:088]: Attempting to delete file C:\WINDOWS\Installer\1f80a9f.msp
MSI (s) (A8:04) [21:28:16:088]: MainEngineThread is returning 1646
MSI (s) (A8:C0) [21:28:16:088]: No System Restore sequence number for this installation.
Uninstallation of the patch package is not supported.
C:\WINDOWS\Installer\181c1.msi
MSI (s) (A8:C0) [21:28:16:088]: User policy value 'DisableRollback' is 0
MSI (s) (A8:C0) [21:28:16:088]: Machine policy value 'DisableRollback' is 0
MSI (s) (A8:C0) [21:28:16:088]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (A8:C0) [21:28:16:088]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (A8:C0) [21:28:16:088]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (A8:C0) [21:28:16:088]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (A8:C0) [21:28:16:088]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (A8:C0) [21:28:16:088]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (A8:C0) [21:28:16:088]: Restoring environment variables
MSI (c) (D4:28) [21:28:16:088]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (D4:28) [21:28:16:088]: MainEngineThread is returning 1646
=== Verbose logging stopped: 11/30/2013 21:28:16 === -
Passing an array of beans to PL/SQL proc - can't quite figure it out
Hi
I'm trying to pass in a Java array of beans to a PL/SQL proc and I can't quite get it to work. I did have the more simple case of an array of strings working but I'm stumped as to how to get this more complicated case to work.
I'm using Java 5 and Oracle 10.
My Oracle User Defined Types
create or replace type MY_OBJECT as object (
id integer,
join_table_name varchar(30)
create or replace type MY_OBJECT_ARRAY as table of MY_OBJECT;
My PL/SQL proc
create or replace package threshold is
function validateThresholdSequence (
thresholdSeqId integer,
testValue number,
testDate date,
validationCriteria in MY_OBJECT_ARRAY
) return number;
end;
My Java
public class ThresholdValidationCriteriaBean
private String joinTableName = null;
private Integer id = null;
//Getters and setters...
//Map my bean to the PL/SQL UDT - thought this might help but it seems not!
Map<String, Class<?>> map = c.getTypeMap();
map.put("MY_OBJECT", ThresholdValidationCriteriaBean.class);
//Prepair my statement
String sql=new String("{call threshold.validateThresholdSequence(?,?,?,?) }");
ps= c.prepareStatement(sql);
// Set the values to insert
ps.setInt(1, thresholdSequenceId);
ps.setDouble(2, testValue);
ps.setDate(3, new java.sql.Date(date.getTime()));
//Sort out the array thing
ArrayDescriptor desc = ArrayDescriptor.createDescriptor("MY_OBJECT_ARRAY", c);
ThresholdValidationCriteriaBean[] beanArray = new ThresholdValidationCriteriaBean[validationCriteria.size()];
validationCriteria.toArray(beanArray);
ARRAY array = new ARRAY (desc, c, beanArray);
((oracle.jdbc.driver.OraclePreparedStatement)ps).setARRAY(4, array); When I run this I get the following error on the creation of the ARRAY object
java.sql.SQLException: Fail to convert to internal representation: uk.co.cartesian.ascertain.imm.threshold.ThresholdValidationCriteriaBean@15c7850
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
at oracle.jdbc.oracore.OracleTypeADT.toDatum(OracleTypeADT.java:239)
at oracle.jdbc.oracore.OracleTypeADT.toDatumArray(OracleTypeADT.java:274)
at oracle.jdbc.oracore.OracleTypeUPT.toDatumArray(OracleTypeUPT.java:115)
at oracle.sql.ArrayDescriptor.toOracleArray(ArrayDescriptor.java:1314)
at oracle.sql.ARRAY.<init>(ARRAY.java:152)I've spent most of the day so far going from one error to the next - but I seem to be stuck now.
Any help or hints very much appreciated
Cheers
Ian
Edited by: Yanis on Feb 28, 2008 12:12 PMI've found the answer - I'll put the code here so everyone else can see what seems to work for me
First off the object that is being passed into the array needs to implement a couple of interfaces and so becomes
public class ThresholdValidationCriteriaBean
implements SQLData, Serializable
private String joinTableName = null;
private Integer id = null;
//Getters and Setters
public String getSQLTypeName()
throws SQLException
return "MY_OBJECT";
public void readSQL(SQLInput stream, String typeName)
//No need to implement this
public void writeSQL(SQLOutput stream)
//No need to implement this
}The code that I used to call the PL/SQL procedure with an array of MY_OBJECT's is
//Sort out our array stuff
ArrayDescriptor desc = ArrayDescriptor.createDescriptor("MY_OBJECT_ARRAY", c);
ThresholdValidationCriteriaBean[] ba = new ThresholdValidationCriteriaBean[validationCriteria.size()];
//Populate array
ARRAY arrayToPass = new ARRAY (desc, c, ba);
//Create our statement
String sql = new String("{call ? := threshold.validateThresholdSequence(?,?,?,?) }");
ps = c.prepareCall(sql);
//Register our out parameter
((oracle.jdbc.OracleCallableStatement)ps).registerOutParameter(1, Types.INTEGER);
// Set the values to insert
ps.setInt(2, thresholdSequenceId);
ps.setDouble(3, testValue);
ps.setDate(4, new java.sql.Date(date.getTime()));
((oracle.jdbc.driver.OraclePreparedStatement)ps).setARRAY(5, arrayToPass);
//Execute call to PL/SQL
ps.execute(); Edited by: Yanis on 10-Mar-2008 13:17 -
I have a macbook pro 15" Retina. I have notifications activated.
The problem is my friend logged into his twitter account and I now always get notifications for his twitter. How do I delete his account from my notifications?
I went Safari> Preferences> Notifications and there is no twitter account in the list, there's no list of any . This is what I got -
Just - the free dictionary. No other registered notifications??
Maybe you are looking for
-
0FISCPER text variable "External Characteristic Value Key" has changed
Hello! Could somebody help and tell, why in BI7.0 version (but 3.x RRMX version) the format of the 0FISCPER text variable (also other time characteristics) has changed from 001.2007 (version 3.x) to 0/1 .0700 (version 7.0)? I cannot understand the l
-
Creating a PDF via printing in Mac O.S.
Hello, I am new to Mac so pardon my ignorance here. I am using Adobe XI Professional on a Mac and would like to print an Adobe document I have filled-in/ created as a PDF file; specifically, a portion of the file. For instance, in Windows, I would s
-
Extended desktop option with win xp
When using bootcamp and winxp (have to because of the software) I am unable to get the 2nd monitor to run (works fine when i boot under mac os) I'm using a macbook pro with the ati 1600x card. does anyone have any ideas about how to enable the extend
-
Problems displaying album artwork
for some reason, my video ipod won't display some of the album artwork from itunes. it shows the downloaded song artwork and some other songs, but not others (like when i import one of my CD's and the itunes library automatically finds the album artw
-
Easily identify Exchange Invites?
I have switched over to using Mail in Snow Leopard with my companies Exchange 2007 server from Entourage. Overall I am MUCH happier, but there are a few things I am still trying to work out. One of them is how to easily identify meeting invites. When