No commit message

When i'm committing some changes and some business rules are violated the 'message-window' appear. After correcting the errors and commiting the changes i'm not getting the usual 'commit-message'. This only happens after i got the 'message-window'.
P.S. I'm using the client-server-option of Headstart.

Lauri,
Which headstart-version i'm using: i've installed 6.5.0.1 from CD and applied the patches 6.5.2.1 and 6.5.2.2. At last i've installed the 6.5.2.2 client-server option.
The messages are displayed in an alert. I think this is default because i didn't change it.
Regards,
Richard

Similar Messages

No commit-message (FRM-40400) == Bug in Headstart

Hello,
On committing on or more business rules are violated the 'message-window' appear.
After correcting the errors and committing the changes i'm not getting the usual
'commit-message' (FRM-40400). This only happens after on or more business rules are violated.
This is caused by a bug in the procedure 'QMS$FORMS_ERRORS.PUSH'. Below the solution i have implemented (the complete procedure is displayed). I'm using version 6.5.4.0 of the library 'qmslib65.pll.
PROCEDURE Push
( p_msg IN VARCHAR2
, p_error IN VARCHAR2 DEFAULT 'I'
, p_msg_type IN VARCHAR2 DEFAULT ''
, p_msgid IN NUMBER DEFAULT 0
, p_loc IN VARCHAR2 DEFAULT '') IS
-- Purpose Show message to the end-user, standard procedure for the Oracle Forms
-- Generator of Designer/2000 to pass the display and handling of a message
-- to a user created procedure.
-- Usage Called by the Oracle Forms Generator code
-- Parameters : msg Text message
-- error ERRor or WARNing
-- msg_type ORA, API or user TLA
-- msg_id Id of message
-- loc Location where error occured
-- Remarks
v_msg VARCHAR2(2000) := p_msg;
v_error VARCHAR2(2000) := p_error;
v_servermsg VARCHAR2(2000) := DBMS_ERROR_TEXT;
l_empty_errorrec hil_Message.message_rectype;
BEGIN
IF p_msgid != 0
THEN
g_errorrec.severity := p_error;
ELSIF ((SUBSTR (v_msg, 1, 11) = 'API Error: ')) OR
((INSTR (v_servermsg, 'ORA-20999') <> 0) AND (v_msg IS NULL)) OR
(INSTR (v_msg, 'ORA-20999') <> 0)
THEN
-- error returned from the API, just display no further action required ?
HandleServerAPIError (p_msg);
-- M. Kappel
/* 11-apr-2001
- Allow check of v_servermsg even if v_msg contains data.
- With new-style cdm ruleframe, v_msg contains 'ORA-20998'.
We never looked at v_servermsg because v_msg was not null.
- With old-style database trigger business logic, v_msg contains only text.
If we still never look at v_servermsg, we don't identify that the error is
a 20998 and therefore we raise an alert 'Transaction Failed' instead of
showing the 'Errors in this Transaction' window.
-- ELSIF ((INSTR (v_servermsg, 'ORA-20998') <> 0) AND (v_msg IS NULL)) OR
-- (INSTR (v_msg, 'ORA-20998') <> 0)
-- THEN
On committing on or more business rules are violated the 'message-window' appear.
After correcting the errors and committing the changes i'm not getting the usual
'commit-message' (FRM-40400). This only happens after on or more business rules are violated.
When one or more business rules are violated application error ORA-20998 is raised. To
detect this DBMS_ERROR_TEXT is used ==> DBMS_ERROR_TEXT contains ALWAYS the text of the
LAST (dbms-)error (the text contains 'ORA-20998').
Even when no business rules are violated it's possible that DBMS_ERROR_TEXT contains 'ORA-20998'.
In that case no FRM-, MNU-, PLS-, SRW-, ORA- or REP-messages are displayed, because the error is
treated as a voilation of one or more business rules. To avoid this 'v_error = E' is added to the IF-clause:
when one or more business rule are violated this procedure is called to display an error (p_error ==> E);
for displaying the FRM-, MNU-, PLS-, SRW-, ORA- and REP-messages this procedure is called to display an
information (p_error ==> I).
When Designer generates code to validate p.e. check-constraints it will call this procedure too. See the example
below:
IF (:FUNCTIES.MIN_LEEFTIJD < :FUNCTIES.MAX_LEEFTIJD) THEN
NULL;
ELSE
qms$forms_errors.push('CBB-00219', 'E', 'OFG', 0);
qms$forms_errors.raise_failure;
END IF;
In this case the procedure is called to display an error. To avoid that the error is incorecctly treated as a
violation of one or more business rules '(p_msg_type != 'OFG' or p_msg_type is null)' is added to the IF-clause.
ELSIF v_error = 'E'
AND (p_msg_type != 'OFG' or p_msg_type is null)
AND ( INSTR (v_servermsg, 'ORA-20998') <> 0
OR INSTR (v_msg, 'ORA-20998') <> 0
THEN
HandleServerApplError (p_msg);
-- error returned from the API, just display no further action required ?
ELSIF ((INSTR (v_servermsg, 'ORA-20000') <> 0) AND (v_msg IS NULL)) OR
(INSTR (v_msg, 'ORA-20000') <> 0)
THEN
-- error was raised by old Headstart code with raise_application_error
-- strip ora-20000 : , check if code (get message) or message
HandleOldHeadstart (v_servermsg);
ELSIF (SUBSTR (v_msg, 1, 3) IN ('FRM', 'MNU', 'PLS', 'SRW', 'ORA', 'REP'))
THEN
HandleOracleError (v_msg, v_error);
ELSE
HandleApplError(v_msg, v_error);
END IF;
Display_Error (g_errorrec);
g_errorrec := l_empty_errorrec;
END Push;

you can create a KEY-COMMIT form level trigger with the following :
declare
msglvl varchar2(3) := :system.message_level ;
begin
:system.message_level := 5 ;
commit_form ;
:system.message_level := msglvl ;
end ;
or put instruction : clear_message; before the commit_form ;

How to fetch a package's commit messages as text?

I use a set of my own scripts for building everything from abs/aur from source. I track dependencies, including makedepends, package groups, package splits, etc by scanning PKGBULDs to extract the info into my database. My build script attempts to automatically show me the README and configuration options via "configure --help" or "cmake -LH", and after the package is built it shows me the namcap output so that I can approve the build and go on or change the PKGBUILD to correct errors.
I would really like to have my build script also show me the changelog, as a text file, for the package by fetching the commit messages from the Arch web interface, such as http://projects.archlinux.org/svntogit/ … &showmsg=1, but I don't know how to fetch that dynamic page as a text file.
If it were a simple static page like the main page for archlinux.org I could get it with lynx -dump or html2text, but these don't give me anything useful for the package's "View Changes" pages.
I hope that seems like a simple problem to someone. Please give me a clue how to fetch dynamic pages like that as text...
Last edited by sitquietly (2012-02-03 20:56:44)

karol wrote:Have you seen https://bbs.archlinux.org/viewtopic.php?id=134591 ?
Yes, of course, and it may be helpful if I have to dig into it's code, but by itself it gives markup (colorized text intended for a terminal emulator) rather than plain text. If I dump its output into vim I still have what looks like trash. I could filter out the markup. Argh.
Any other help out there??

Commit message behaviour problem

Hi all,
I'm using forms6i in C/S mode.
I have a form program that after commit would display an alert and ask user whether to re-direct to another form. The form normally commits and would display the standard message "Transaction complete: 1 records applied and saved" in the system message bar at the bottom. However, when I answer the re-direct alert button and call a new form, a dialogue box always appear with the transaction complete message.
Any ideas how I can disable this annoying dialogue box?
Any suggestion would be appreciated!
Thanks,

Hi Duncan & Kevin,
Here's the program flow:
1)At key-commit trigger I commit and do a re-query to refresh the form.
2)Then I check whether the program needs to re-direct to another form.
3)If re-direct is required then pop-up an Alert to ask user whether to re-direct or cancel. If Cancel the form would update a field and do another commit. for re-direct, it simply call a new form using call_form.
Now, I set the message_level before step 3. The actual behaviour is that if user select cancel, the Transaction Complete simply display in the system message line at the bottom of the screen. However, if user select re-direct, then a pop-up dialogue box showing the Transaction Complete message is displayed.
How can I suppress the dialogue box but not the message on the system message line. I don't want user to click an OK button for that message.
Thanks a lot

How can i give commit message.

Dear All,
i have create a form using view object.
when i create new record using createInsert operation after that i have used commit button.
Record Saved successfully into data base.
but how i give Message to browser(client)
like
Record Inserted successfully.
Manish

something like this?
    public String save() {
        // Add event code here...
        BindingContainer bindings = getBindings();
        OperationBinding operationBinding = bindings.getOperationBinding("Commit");
        Object result = operationBinding.execute();
        if (!operationBinding.getErrors().isEmpty()) {
            FacesContext ctxs = FacesContext.getCurrentInstance();
            FacesMessage fms = new FacesMessage(FacesMessage.SEVERITY_INFO, "Data are not commited", "");
            ctxs.addMessage(null, fms);
        else {
            FacesMessage fm = new FacesMessage("Data's Commited Succesfully");
            fm.setSeverity(FacesMessage.SEVERITY_INFO);
            FacesContext context = FacesContext.getCurrentInstance();
            context.addMessage(null, fm);
        return null;
    }

Re: Test commit message

That looked bad, another test.
Short mixed
Below
Med mixed
Message below header
Longer mixed
Another message below longer dashes
Just asterisks
Now let's do dashes

Hi,
there is some change in the XMLSPy4.3/XMLType Library 1.2 :
Validation
One common task on documents is to validate them against an assigned schema or DTD. If the XML file has no schema or DTD already assigned, use "Document.AssignSchema" or "Document.AssignDTD" to add the necessary references to the document.
Examples:
objSpy.ActiveDocument.AssignSchema "C:\mySchema.xsd", False
or
objSpy.ActiveDocument.AssignDTD "C:\myDTD.dtd", False
If you want the user to select a schema or DTD, pass True as the second parameter to these functions to display a file-dialog. These methods only put the reference into the document and do not check the existence of the specified file. If the file path is not valid, the validation will fail.
After you have assigned a valid schema or DTD reference to your file, you are able to validate it with "Document.IsValid". IsValid needs some out-parameters that must be declared as VARIANTs to be accessible from script languages like VBScript and JavaScript.

Message is not getting displayed.

Hi all,
I have a form with KEY_COMMIT Trigger with the code below:
DECLARE
cls_date DATE;
Duration NUMBER;
int_rate NUMBER(3,2);
PA_AMT    NUMBER(10,2);
TRMS      NUMBER;
I_RATE    NUMBER(4,2);
pl_id ParamList;
usernm VARCHAR2(20);
OLD_FDR_NO NUMBER;
BEGIN
PA_AMT:=:KEC_FDACCT_MSTR.AMOUNT;
TRMS:=SUBSTR(:GROUP_TYPE,1,2);
commit_form;
SELECT INT_RATE INTO I_RATE FROM FDSLAB_MASTR WHERE GROUP_TYPE=:GROUP_TYPE AND FDSLAB_NO=:KEC_FDACCT_MSTR.ACCT_TYPE;
DUARATION_DTL(PA_AMT,TRMS,I_RATE);
message('3- I want this message to be displayed.This is not getting displayed');
message(' ');
SELECT sap_code INTO :KEC_FDACCT_MSTR.sap_code FROM FDSLAB_MASTR WHERE GROUP_TYPE=:GROUP_TYPE AND FDSLAB_NO=:KEC_FDACCT_MSTR.ACCT_TYPE;
commit_form;
END;
In the above code, you can find DUARATION_DTL(PA_AMT,TRMS,I_RATE);
DUARATION_DTL is a Procedure which is coded in the Program Unit with the below code.
PROCEDURE DUARATION_DTL(PAMT NUMBER,QTR NUMBER,RATE NUMBER) IS
.........SOME variables declared..........
BEGIN
SOME IF ELSE statements
SOME INSERT statements
SOME UPDATE statements
COMMIT;
message('FDR No Saved Successfuly'||:KEC_FDACCT_MSTR.ACCT_FD_NO);
message('');
END;
When I run the form, Message('3') that is the message marked is not getting displayed.
Only the message in procedure DUARATION_DTL that is in green is getting displayed.
Can you let me know why?
Is there anything i should do to display this message,
Or is it because its buggy??
Help me please.
Thank You.
Oracle Forms 6i.
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production

Hi AW, I actually don't want to display that message.
I want to know why is that message not getting displayed??
Is that because of the following Triggers??
Trigger:ON_MESSAGE:
if MESSAGE_CODE = 40400 then
message('FDR information saved successfully.');
message('');
else
message(MESSAGE_TEXT);
end if;
Trigger:ON_ERROR:
if ERROR_CODE = 40202 then
message('This field cannot be blank');
message(' ');
RAISE form_trigger_failure;
elsif ERROR_CODE = 41800 then
message('List of values is not available for this field.');
message(' ');
RAISE form_trigger_failure;
elsif ERROR_CODE = 40401 then
null;
else
message(ERROR_TEXT);
message(' ');
RAISE form_trigger_failure;
end if;
These above mentioned triggers are present in the form.
Is it because of these triggers , that the message is not getting displayed??
If yes, can you tell me why?

Transactional triggers and commit processing

I have only been an active member of this thread for a couple of weeks and have tried to contribute to a few postings. But I have also noticed lots of postings relating to the use of DML statements inside what I would call non commit time triggers.
What I mean here is, for example, a WHEN-BUTTON-PRESSED trigger that does inserts, updates, deletes, followed by the COMMIT_FORM procedure.
I thought it might be useful to draw attention to the possible pitfalls of this approach. I'm not saying that this approach is wrong - far from it, but sometimes it means that people aren't leveraging the functionality that you get "for free" from Forms.
By coding some DML followed by a Commit_Form, you are not getting any rollback functionality from Forms. For example:
INSERT INTO A
INSERT INTO B
COMMIT_FORM;
Let's imagine that the insert into A worked but the insert into B failed for some reason. The user gets an unhandled exception. Now imagine that the cause of the error is cleared up, and the user presses the button (or whatever the invokation action was) again, and the commit works. You will have 2 records in A and 1 in B. You may not have expected that, and without coding your own rollback/savepoint that's what you would get.
You also (1) don't get a Working... message without coding it yourself, and (2) get the "No changes to commit" message; removing this is the subject of many threads on this site.
If you have a block which is based over a table which you need to update, then all of the DML statements ought to be coded inside PRE/POST/ON INSERT/UDPATE/DELETE statements, or other Forms transactional triggers (pre-database-commit etc..). If you need to change other tables then put the DML for them inside those triggers. Then you don’t have to worry about which records the user changed – if the user didn’t touch them then Forms won’t fire the triggers. And when you call the COMMIT_FORM procedure, Forms will fire the triggers for you and if any of them fail, it will rollback back to where the COMMIT_FORM started.
An example in 1 thread I saw this morning, was a Delete button, which was to delete the current record in a multi-record block. This button performed the “DELETE FROM <table> WHERE <key=:block.key>” followed by a Commit. Then of course the block needed to be re-queried to reflect the fact that the record had gone. Using the power of Forms to simply call the DELETE_RECORD procedure would have achieved the same result without needing to requery the block. And Forms would do the delete by ROWID, the fastest way of doing it.
If you don’t have a block based over a table, then you can consider creating a dummy block which uses Transactional Triggers. Code an ON-INSERT on that block which includes the DML you want to execute. Then in the trigger initiating the commit processing you would do something like:
:DUMMY_BLOCK.ITEM1 := ‘X’;
COMMIT_FORM;
IF (NOT FORM_SUCCESS) OR :SYSTEM.FORM_STATUS != ‘QUERY’ THEN
-- the commit failed
END IF;
Then you’ll get a nice Working.. message and full rollback control.
I think the moral of what I’m trying to get across is to use the power of Forms in the way it handles the transactions. Whilst we moan about it, it is actually quite good at that!
I hope this posting is taken in a positive light, I am certainly not trying to teach anyone to “suck eggs”.
PS. I find it ironic that you were prevented from coding DML statements outside of commit time triggers, in Forms 2.3!

Thank you, Kevin. Very informative.

Transaction does not commit

I have a JDBC transaction that is not committing to the database, but is also not throwing an error.
The scenario is this:
JMS message arrives on transactional queue
Message processed by MDB
MDB calls several Sybase ASE stored procedures
JDBC transaction is rolled back, JMS message is not.
I believe this to be specific to WLS 8.1. I set up two test environments where everything was the same except for the WLS version.
Same OS (windows), same JDBC driver, same database, same application code. WLS 8.1 SP4 and SP5 do not work. WLS 9.1 works.
I tried using JTS debugging, and the log says it commits the transaction. A query just prior to the MDB exiting confirms that the data is in the database and correct, but as soon as the MDB exits the data rolls back, despite the JTS commit message.
The biggest roadblock here is that I am unable to upgrade our production environment to WLS 9.1, so I need to get this working on WLS 8.1.
Can anyone offer some insight into this? I'd really appreciate it.
Craig

Further testing has revealed that I can get it to work on WLS 8.1 by disabling connection testing in the pool.

Enabling any one of the connection testing options (test reserved, test created, or test released) causes the JDBC transaction to get silently rolled back.

We're using Sybase Adaptive Server Enterprise/12.5.3/EBF 12868 ESD#4/P/Sun_svr4/OS 5.8/ase1253/1923/32-bit/FBO/Thu Sep 8 14:14:28 2005.

Is there a known "Test Table Name" that works?

I've tried several different options including:
<ul>
<li>SQL SELECT 1 from sysobjects</li>
<li>SQL SELECT @@version</li>
<li>SQL SELECT count(*) from tablename</li>
<li>SQL SELECT count(*) from db..tablename</li>
<li>SQL SELECT count(*) from db.user.tablename</li>
</ul>
Any help would be greatly appreciated.

The messages not dequeue

I have a separate installation of Sun Java Communications Suite 6u2
frontend: WebServer,Communication Express, messaging (front) and Calendar (front)
midleTier: Delegated Administrator, webserverand Access Manager
backend: Directori Server, Messaging(store) and Calendar (Store)
User: [email protected] sent mailtest to [email protected], but is queue in the frontend, i write imsimta qm release -all, but still queue in the frontend.
################ hostname = fiec-frontend.fiecup.org
bash-3.00# ./imsimta version
Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)
libimta.so 7u2-7.05 32bit (built 17:05:39, Jul 30 2009)
Using /opt/sun/comms/messaging/config/imta.cnf (compiled)
SunOS fiec-frontend 5.10 Generic_120011-14 sun4u sparc SUNW,Ultra-4
bash-3.00#
bash-3.00# ./imsimta qm dir -envelope
Sun, 27 Sep 2009 14:30:00 -0500 (GMT+5)
Data gathered from the queue directory tree
Channel: tcp_intranet
From To Size Queued since
1 [email protected] @fiec-backend.fiecup.org: 2 27 Sep 09 00:04
2 [email protected] @fiec-backend.fiecup.org: 2 26 Sep 09 23:03
3 [email protected] @fiec-backend.fiecup.org: 2 26 Sep 09 23:22
Total size: 6
Grand total size: 6
bash-3.00#
bash-3.00# ifconfig -a
lo0:1: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
hme0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 201.225.136.53 netmask fffffff8 broadcast 201.225.136.55
hme1:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 192.168.100.3 netmask ffffff00 broadcast 192.168.100.255
bash-3.00#
bash-3.00# netstat -rn
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
default 201.225.136.49 UG 1 759
192.168.100.0 192.168.100.3 U 1 0 hme1:1
201.225.136.48 201.225.136.53 U 1 65 hme0:1
224.0.0.0 192.168.100.3 U 1 0 hme1:1
127.0.0.1 127.0.0.1 UH 20 10919 lo0:1
bash-3.00#
bash-3.00# vi mail.log_yesterday
26-Sep-2009 23:22:41.22 tcp_intranet tcp_intranet EE 2 [email protected] rfc822;[email protected] @fiec-backend.fiecup.org:[email protected] <fbd99fed355c.4abea
[email protected]> mailsrv TCP|192.168.100.3|25|192.168.100.3|64687
26-Sep-2009 23:22:41.22 > Received: from [192.168.100.3] (Forwarded-For: 190.141.94.2) by fiec-frontend.fiecup.org (mshttpd); Sat, 26 Sep 2009 23:22:40 -0500
27-Sep-2009 00:04:30.96 tcp_intranet tcp_intranet EE 2 [email protected] rfc822;[email protected] @fiec-backend.fiecup.org:[email protected] <fbdd94f8585.4abeac
[email protected]> mailsrv TCP|192.168.100.3|25|192.168.100.3|33238
27-Sep-2009 00:04:30.96 > Received: from [192.168.100.3] (Forwarded-For: 190.141.94.2) by fiec-frontend.fiecup.org (mshttpd); Sun, 27 Sep 2009 00:04:30 -0500
bash-3.00# ./configutil
local.hostname = fiec-frontend.fiecup.org
local.imta.enable = 1
local.mmp.enable = 1
local.purge.enable = 0
local.sched.enable = 1
local.schedule.expire = "0 23 * * * bin/imexpire"
local.schedule.expire.enable = 0
local.schedule.msprobe = "5,15,25,35,45,55 * * * * lib/msprobe"
local.schedule.purge = "0 0,4,8,12,16,20 * * * bin/imsimta purge -num=5"
local.schedule.purge.enable = 1
local.schedule.return_job = "30 0 * * * lib/return_job"
local.schedule.return_job.enable = 1
local.schedule.snapshot = "0 2 * * * bin/imdbverify -s -m"
local.schedule.snapshot.enable = 0
local.schedule.snapshotverify = "1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31,33,35,37,39,41,43,45,47,49,51,53,55,57,59 * * * * bin/imdbverify -m"
local.schedule.snapshotverify.enable = 0
local.servergid = mail
local.serveruid = mailsrv
local.service.http.proxy.adminpass = svn450-f13cvp
local.service.http.smtpauthpassword = svn450-f13cvp
local.service.proxy.adminpass = svn450-f13cvp
local.store.enable = 0
local.ugldapbasedn = "dc=fiecup,dc=org"
local.ugldapbindcred = f0`_7NgPrG
local.ugldapbinddn = "uid=msg-admin-fiec-frontend.fiecup.org-20090927033106Z, ou=People, o=fiecup.org,dc=fiecup,dc=org"
local.ugldaphost = fiec-backend.fiecup.org
local.ugldapport = 389
local.watcher.enable = 1
local.webmail.sso.amcookiename = iPlanetDirectoryPro
local.webmail.sso.amnamingurl = http://fiec-midle.fieup.org:80/amserver/namingservice
local.webmail.sso.singlesignoff = yes
local.webmail.sso.uwccontexturi = uwc
local.webmail.sso.uwcenabled = 1
local.webmail.sso.uwchome = http://fiec-frontend.fiecup.org:80/uwc
local.webmail.sso.uwcport = 80
service.dcroot = "dc=fiecup,dc=org"
service.defaultdomain = fiecup.org
service.http.enable = 1
service.http.port = 81
service.imap.enable = 0
service.pop.enable = 0
store.serviceadmingroupdn = "cn=Service Administrators,ou=Groups, dc=fiecup,dc=org"
bash-3.00#
################ hostname fiec-backend.fiecup.org
bash-3.00# ifconfig -a
lo0:3: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
hme1:3: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 192.168.100.1 netmask ffffff00 broadcast 192.168.100.255
bash-3.00#
netstat -rn
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
192.168.100.0 192.168.100.1 U 1 0 hme1:3
224.0.0.0 192.168.100.1 U 1 0 hme1:3
127.0.0.1 127.0.0.1 UH 28 49165 lo0:3
bash-3.00#
please help me!

this is a new installation
bash-3.00# ./imsimta qm dir -envelope
Tue, 29 Sep 2009 07:43:59 -0500 (GMT+5)
Data gathered from the queue directory tree
Channel: tcp_local
From To Size Queued since
1 [email protected] [email protected] 2 27 Sep 09 15:37
2 [email protected] [email protected] 1 27 Sep 09 15:29
Total size: 3
Channel: tcp_intranet
From To Size Queued since
3 [email protected] @fiec-backend.fiecup.org: 2 28 Sep 09 09:27
@fiec-backend.fiecup.org:
4 [email protected] @fiec-backend.fiecup.org: 5 27 Sep 09 15:40
5 [email protected] @fiec-backend.fiecup.org: 2 27 Sep 09 15:33
Total size: 9
Grand total size: 12
bash-3.00#
bash-3.00# more mail.log
27-Sep-2009 15:33:27.79 tcp_intranet tcp_intranet EE 2 [email protected] rfc822;[email protected] @fiec-backend.fiecup.org:[email protected] <fbdde74d6257.4abf8
[email protected]> mailsrv TCP|192.168.100.3|25|192.168.100.3|35081
27-Sep-2009 15:37:45.61 tcp_intranet tcp_local EE 2 [email protected] rfc822;[email protected] [email protected] <[email protected]>
mailsrv TCP|192.168.100.3|25|192.168.100.3|35226
27-Sep-2009 15:40:55.17 tcp_local tcp_intranet EEC 5 [email protected] rfc822;[email protected] @fiec-backend.fiecup.org:[email protected] <COL120-W2A3E
[email protected]> mailsrv TCP|201.225.136.53|25|65.55.34.89|18394
bash-3.00#
bash-3.00# more job_controller.log-0KQN00100KK0VY00
/opt/sun/comms/messaging/lib/smtp_client: can't get execution attributes
/opt/sun/comms/messaging/lib/smtp_client: can't get execution attributes
/opt/sun/comms/messaging/lib/smtp_client: can't get execution attributes
whht is means?

Messaging in solaris 10

i have a customer setup with 490 server with solaris 10 ( all patch included) and suncluster3.2. customer wants all console messaging ( dev/sysmsg) to be included into system message(/var/adm/messages) or to be redirected to any other file. i have tried with /etc/syslog.conf or consadm. does anyone who can suggest me on the same ?
thanks in addvance.
skd

Hi Shane,
Thanks for reply.
The output of "./imsimta version:
+Sun Java(tm) System Messaging Server 7.0-0.04 32bit (built Jun 20 2008)+
+libimta.so 7.0-0.04 32bit (built 01:01:00, Jun 20 2008)+
+Using /opt/sun/comms/messaging/config/imta.cnf+
+SunOS mail 5.10 Generic_120012-14 i86pc i386 i86pc+
Internal mail means all domains which have created in our server and when we send mail within domain or in same domain, UID must be validated.
Thanks
Prem

All FRM messages are suppressed after buissness rules validation

hello,
i've just discovered this really odd and annoying problem and I need some help. After validating business rules all forms messages are suppressed. If I re-enter the form, messages appear again, but are "visible" only till next business rules validation.
this is the scenario:
1. When I enter the form, I disable all business rules
2. I insert some data and commit. Message FRM-40400 appears.
3. I validate business rules by pressing button "Validate" (I call procedure which enables all business rules, calls procedure capi.validate_all_static_br, disables business rules and displays errors with Qms$errors.RaiseQMSFailure)
4. if i change some data and commit, message FRM-40400 does not appear.
I've done some debugging and discovered problem in qmslib65.pll package qms$forms_errors procedure push
PROCEDURE Push
( p_msg IN VARCHAR2
, p_error IN VARCHAR2 DEFAULT 'I'
, p_msg_type IN VARCHAR2 DEFAULT ''
, p_msgid IN NUMBER DEFAULT 0
, p_loc IN VARCHAR2 DEFAULT '') IS
-- Purpose Show message to the end-user, standard procedure for the Oracle Forms
-- Generator of Designer/2000 to pass the display and handling of a message
-- to a user created procedure.
-- Usage Called by the Oracle Forms Generator code
-- Parameters : msg Text message
-- error ERRor or WARNing
-- msg_type ORA, API or user TLA
-- msg_id Id of message
-- loc Location where error occured
-- Remarks
v_msg VARCHAR2(2000) := p_msg;
v_error VARCHAR2(2000) := p_error;
v_servermsg VARCHAR2(2000) := DBMS_ERROR_TEXT;
l_empty_errorrec hil_Message.message_rectype;
BEGIN
IF p_msgid != 0
THEN
g_errorrec.severity := p_error;
ELSIF ((SUBSTR (v_msg, 1, 11) = 'API Error: ')) OR
((INSTR (v_servermsg, 'ORA-20999') <> 0) AND (v_msg IS NULL)) OR
(INSTR (v_msg, 'ORA-20999') <> 0)
THEN
-- error returned from the API, just display no further action required ?
HandleServerAPIError (p_msg);
-- M. Kappel
/* 11-apr-2001
- Allow check of v_servermsg even if v_msg contains data.
- With new-style cdm ruleframe, v_msg contains 'ORA-20998'.
We never looked at v_servermsg because v_msg was not null.
- With old-style database trigger business logic, v_msg contains only text.
If we still never look at v_servermsg, we don't identify that the error is
a 20998 and therefore we raise an alert 'Transaction Failed' instead of
showing the 'Errors in this Transaction' window.
-- ELSIF ((INSTR (v_servermsg, 'ORA-20998') <> 0) AND (v_msg IS NULL)) OR
-- (INSTR (v_msg, 'ORA-20998') <> 0)
-- THEN
ELSIF (INSTR (v_servermsg, 'ORA-20998') <> 0) OR
(INSTR (v_msg, 'ORA-20998') <> 0)
THEN
HandleServerApplError (p_msg);
-- error returned from the API, just display no further action required ?
ELSIF ((INSTR (v_servermsg, 'ORA-20000') <> 0) AND (v_msg IS NULL)) OR
(INSTR (v_msg, 'ORA-20000') <> 0)
THEN
-- error was raised by old Headstart code with raise_application_error
-- strip ora-20000 : , check if code (get message) or message
HandleOldHeadstart (v_servermsg);
ELSIF (SUBSTR (v_msg, 1, 3) IN ('FRM', 'MNU', 'PLS', 'SRW', 'ORA', 'REP'))
THEN
HandleOracleError (v_msg, v_error);
ELSE
HandleApplError(v_msg, v_error);
END IF;
Display_Error (g_errorrec);
g_errorrec := l_empty_errorrec;
END Push;
IMO, this part of code
ELSIF (INSTR (v_servermsg, 'ORA-20998') <> 0) OR
(INSTR (v_msg, 'ORA-20998') <> 0)
is either obsolete or incomplete. It should be something like this:
ELSIF (INSTR (v_servermsg, 'ORA-20998') <> 0 AND(v_msg IS NULL)) OR (INSTR (v_msg, 'ORA-20998') <> 0)
i would like to know if anyone have simmilar problem and if there are any other solutions then above mentioned.
Kind regards,
Damjan

I'm having the same problem, i'm using 6.5.22 with the C/S-kit
Is there already a solution for this problem?
Regards,
Richard Teunissen

Not to display Yes/No/Cancel message window, while closing Oracle Apps Form

Hello All,
I have a requirement,where we need to avoid displaying Yes/No/Cancel message window when trying to save the changes in Oracle Applications Form.
Please do let me know how to achive this.
Thanks a lot in Advance.

Hi Ramesh,
Thanks for the Update.
I have used the below code in KEY-EXIT
CLEAR_FORM(NO_VALIDATE);
EXIT_FORM;
Also the code behind the button which submits the conc.program:
DECLARE
l_request_id NUMBER;
vRESP_APPL_ID number;
vRESP_ID number;
vUSER_ID number;
BEGIN
--vRESP_APPL_ID := apps.FND_PROFILE.VALUE('RESP_APPL_ID');
--vRESP_ID := apps.FND_PROFILE.VALUE('RESP_ID');
--vUSER_ID := apps.FND_PROFILE.VALUE('USER_ID');
--apps.FND_GLOBAL.APPS_INITIALIZE(vUSER_ID,vRESP_ID,vRESP_APPL_ID);
apps.FND_GLOBAL.APPS_INITIALIZE(2340,20420,1);
l_request_id := FND_REQUEST.SUBMIT_REQUEST ('XXAHS',
          'XXAHSRPDSR',
     null,
                    sysdate,
                    FALSE,
                    '|020|080|031|161|030|100|131|',
                    '11-JAN-10',
                    '|41|42|43|45|',
insert into temp_amk values(15);
commit;
message('request id:'||l_request_id);
exception
when others then
message(sqlerrm);
end;
This code worked fine, in case I ran from SQL Prompt.
Please let me know what must be missing.
Thanks.

Convergence and messaging server http access

Hi,
Sun Java(tm) System Messaging Server 7.0-0.04 32bit (built Jun 20 2008)
libimta.so 7.0-0.04 32bit (built 01:01:00, Jun 20 2008)
Using /opt/sun/comms/messaging/config/imta.cnf
# /opt/sun/comms/iwc/sbin/iwcadmin -V
Sun Convergence 1.0-0.44 (built Jul 07 2008,09:50:03)
Convergence can't login into messaging server:
[06/Nov/2008:21:30:06 +0100] comms httpd[18455]: Account Notice: [x.x.x.x:47323] Password verification failed
[06/Nov/2008:21:30:06 +0100] comms httpd[18455]: Account Notice: badlogin: [x.x.x.x:47323] proxy admin [email protected]: user not found
[06/Nov/2008:21:30:08 +0100] comms httpd[18455]: Account Notice: close [x.x.x.x:47323] [unauthenticated] 2008/11/6 21:30:06 0:00:02 259 247 0
[06/Nov/2008:21:35:01 +0100] comms httpd[18455]: Account Information: connect [127.0.0.1:47369]
[06/Nov/2008:21:35:01 +0100] comms httpd[18455]: General Information: [127.0.0.1:47369] HEAD / HTTP/1.0
[06/Nov/2008:21:35:01 +0100] comms httpd[18455]: Account Notice: close [127.0.0.1:47369] [unauthenticated] 2008/11/6 21:35:01 0:00:00 17 216 0
IMAP/POP/SMTP works - I can use [email protected] from Thunderbird.
Everything works before I created a new domains in Delegated Administrator. Before that Convergence worked with Messaging Server.
Any idea?
Thanks

estibi wrote:
[06/Nov/2008:21:30:06 +0100] comms httpd[18455]: Account Notice: [x.x.x.x:47323] Password verification failed
[06/Nov/2008:21:30:06 +0100] comms httpd[18455]: Account Notice: badlogin: [x.x.x.x:47323] proxy admin [email protected]: user not found
This error is due to the password for the "admin" user being invalid.
Everything works before I created a new domains in Delegated Administrator. Before that Convergence worked with Messaging Server.Try resetting the admin username/password e.g.
./iwcadmin -u <iwcadminuser> -w <iwcadminpass> -o mail.proxyadminid -v [email protected]
./iwcadmin -u <iwcadminuser> -w <iwcadminpass> -o mail.proxyadminpwd -v <adminpassword>Regards,
Shane.

DISTRIBUTED TRANSACTION의 2 PHASE COMMIT 개념 및 절차

제품 : ORACLE SERVER
작성날짜 : 2002-05-15
DISTRIBUTED TRANSACTION의 2 PHASE COMMIT 개념 및 절차
====================================================
Oracle이 분산 트랜잭션 수행을 위해 사용하는 2 phase commit의 자세한 개념
및 절차를 살펴본다.
1. 용어와 개념
Oracle은 분산 트랜잭션을 수행하면서 여기에 포함된 모든 node에 대해서
session tree를 구성한다. session tree는 분산 트랜잭션에 관여되는 session과
각 session의 역할을 계층적인 tree형태로 표현한다고 볼 수 있으며,
DBA_2PC_NEIGHBORS view를 통해 확인 가능하다.
session tree에 포함되는 각 node들이 수행하는 역할은 2 phase commit 절차의
기본적인 개념이 되므로, 분산 트랜잭션의 이해를 위해서 정확히 파악할 필요가
있다. 아래에 각 역할 들의 종류와 의미를 설명하며 [그림 1]을 예로 든다.
- client
- database server
- global coordinator
- local coordinator
- commit point site
insert into seoul_tab...;
delete from pusan_tab@pusan...;
Seoul.world inchoen_procedure@incheon...;
/ \ incheon_procedure source
Pusan.world Inchoen.world ------------------------
\ delete from incheon_tab...;
\ update jeju_tab@jeju...;
Jeju.world
[그림 1] session tree의 간단한 예제
(1) client: 다른 node의 database 정보를 이용하면 client가 된다.
참조되어지는 node는 이때 database server가 된다. seoul.world가
pusan.world와 incheon.world의 client이고, incheon.world는 jeju.world의
client가 된다.
(2) server (database server): 분산 트랜잭션에 포함된 모든 node를 server라
한다. seoul.world, pusan.world, incheon.world, jeju.world 모두 database
server이다.
(3) global coordinator:분산 트랜잭션을 처음 수행시킨 node를 의미한다.
여기서는 seoul.world가 global coordinator이다.
(4) local coordinator: 분산 트랜잭션에서 이 node에 관계된 부분의 결과를
얻으려면 다른 node를 참조해야 하는 경우 이 node를 local coordinator라고
한다. 이것이 위에서 설명한 global coordinator와는 차이가 있는데 global
coordinator는 항상 local coordinator이지만, 반대로 local coordinator는
global coordinator가 아닐 수 있다.
Incheon.world의 경우 처음 문장을 수행시킨 global coordinator는 아니지만,
Incheon.world의 Inchoen_procedure내에 jeju.world가 reference되므로
local coordinator가 된다. seould.world는 global coordinator이면서
local coordinator가 된다.
(5) commit point site
commit point site는 분산 트랜잭션에 관여된 node중 2 phase commit단계에서
commit이나 rollback을 항상 제일 먼저 하게 된다. 이 node의 local
transaction부분은 prepared상태를 거치지 않아 in-doubt 상태가 되는 일이
없고, 그러므로 distributed lock에 의해 조회나 DML시 오류가 발생하는
없게 된다. 이러한 이유로 제일 중요한 data를 포함하는 중심이 되는 node를
commit point site로 지정하는 것이 바람직하다.
commit point site는 각 node의 initialization parameter중
COMMIT_POINT_STRENGTH 값을 비교하여 제일 큰 값을 가진 node가 지정된다.
두 node만 관여된 분산 트랜잭션의 경우 commit_point_strength가 지정되어
있지 않으면, default로 global coordinator가 아닌 node가 commit point
site가 된다.
2. 2 Phase Commit (2PC)
분산 트랜잭션을 commit하는 것은 다음 두 단계를 거치게 된다. 그래서 Oracle의
분산 트랜잭션은 2 phase commit mechanism을 사용한다고 한다.
prepare 단계: global coordinator (SQL문장을 처음 수행한 server) 가 commit
point site를 제외한 나머지 node에게 prepare하도록 요청한다.
요청을 받은 node는 각 local db에서의 작업에 대해 commit이나
rollback할 준비를 마치고 다시 global coordinator에게 prepare
되었음을 알려 주는 단계이다.
node가 prepare 단계를 지나고 commit을 완료하기 전까지는
transaction이 in-doubt상태라고 부른다.
commit단계: 모든 node가 정상적으로 prepare가 되면, 먼저 commit point site가
commit을 완료하고 이후 다른 node들도 commit을 완료하게 된다.
이렇게 분산 트랜잭션에서 commit을 수행하기 위해 두 단계를 거치면서 일부
node만 commit이 되고 일부는 rollback이 되는 불일치 상태를 막을 수 있는데,
그러기 위한 자세한 단계별 처리 절차를 아래 [표 1]에 17단계로 기술하였다.
각 단계별로 global coordinator와 commit point site, 그리고 둘 모두에
해당되지 않는 일반 database server입장으로 나누어 표시하였으며, 만약 어떤
node가 global coordinator이면서 commit point site라면, 두 part의 일을 모두
하게 되는 것이다.
아래 표의 (4) ~ (10)번 단계는 prepare단계의 작업이며, (11) ~ (15)번 단계는 commit단계
이다. 부가적으로 (16), (17)을 정리 단계로 부르기도 한다.
단계| Global coordinator | 참여한 db server | Commit point site
(commit point site도 아니고
global coordinator도 아닌경우)
(1) SQL문장 발생 |     |
(2) SQL문장이 수행되면 session tree가 구성되고 이 정보는
DBA_2PC_NEIGHBORS를 통해 조회 가능하다.
변경이 필요한 data는 각 node별로 자기의 local data에 대해서 lock
(TX,TM)을 걸면서 문장 수행이 진행된다.
(3) Commit; 문장 발생 |          |
(4) commit point site를 |          |
commit_point_strength |          |
initial parameter를 참조 |          |
하여 결정하고, |          |
참여한 모든 node의 SCN중 |          |
제일 큰 값을 commit SCN으로|           |
결정하고 이후에 각 node의 |          |
commit시 이용한다. |          |
(5) commit point site를 |          |
제외한 모든 node들에게 |          |
prepare하도록 요청한다 |          |
(6) prepare 요청 message받는다 |
(7) transaction이 이 node의 data를 변경하였는지를 |
확인하고, 변경 사항이 있고 commit이 가능한 |
상태이면 다음 단계를 수행하고, 그렇지 않으면 |
(10)번 단계로 건너뛴다           |
(8) transaction에 distributed lock을 걸어 fail이 |
되어도 rollback이 되지 않고 변경 사항에 lock이|
걸린 채 유지되도록 한다.           |
distributed lock이 걸려 있는 상태에서는 변경 |
data를 포함한 block에 포함된 어떤 data도 |
read/write가 불가능하게 된다 (ora-1591발생) |
[참조 1]                    |
(9) transaction에 의해 변경된 내용과 (8)번 단계의 |
information에 대한 redo log 내용을 각 node의 |
redo log file에 기록한다. (해당 node의 변경 |
사항만을 해당 node의 redo log file에 기록) |
(10) global coordinator에게 다음 세가지 중 하나의 |
상태를 prepare message대한 응답으로 전달한다.|
PREPARED:변경된 data가 있고 commit이 가능한 |
상태               |
READ-ONLY: 자신의 node에는 data 변경사항이 |
없고 조회만 관여한 경우 |
ABORT: 오류 발생으로 인해 commit이 불가능한 |
경우                     |
(11) prepare 요청 message에 | |
대한 응답 중 한 node라도| |
abort가 있으면: | |
모든 관여된 node를 | |
rollback하도록 요청하고 | |
distributed transaction | |
을 끝낸다. | |
prepare요청 message에 | |
대한 응답이 read-only나 | |
prepared만 있다면: | |
commit point site에게 | |
commit하라고 요청한다. | |
(12) | |이 node에 관여된 local
| |transaction 부분만을
| |commit 한다.
| |- data변경사항과 commit
| |정보를 local redo log
| |file에 기록한다.
| |- commit SCN은 (4)번단계
               |           |에서 얻어진, 관여된 node
               |          |의 SCN중 제일 큰 값을
| | 이용한다.
               |     |- (2) 번 단계에서 잡혔던 TX,
| | TM lock은 해제된다.
(13) |global coordinator에게
|commit이 완료되었음을
|알리는 message를 보낸다.
(14) commit point site를 제 | |
외한 다른 node들에게 | |
commit하라고 요청한다. | |
(15) commit하면서 (2)번 단계에서 잡은 TX, TM lock|
과, (8)번 단계에서 잡힌 distributed lock을 |
release하고, 이러한 commit정보를 redo log |
file에 기록한다.
(16) | |DBA_2PC_PENDING,
| |DBA_2PC_NEIGHBORS등
| |dictionary 저장된 정보를
| |지우고 global coordinator
| |에게 정보를 지웠음을
| |알려준다
(17) DBA_2PC_PENDING, DBA_2PC_NEIGHBORS 등 |
dictionary 저장된 정보를 지우고 정리한다. |
[참조 2] |
[표 1] 2 phase commit의 단계별 절차
[참조 1] distributed lock
(8)번 단계에서 기술한 distributed lock은 실제 v$lock을 확인하여서는
나타나지 않는다. v$lock에 lock type이 DX로 나타나는 것은 distributed
transaction lock으로 이것은 2 phase commit을 위한 것이 아니라
XA에서 단일 transaction내에서 여러 branch에 대한 control을
tightly-coupled 형태로 하는 경우에 사용되어 지는 것이므로, 여기서
언급하는 distributed lock과 혼동되어서는 안된다.
여기에서 설명한 distributed lock은 실제 type을 가지고 있는 lock이
아니고 해당 transaction에 대한 local db내의 rollback segment
header부분에서 transaction상태를 prepared를 나타내는 bit로
     설정함으로써 lock설정을 구현한다.
그러므로 이 lock이 걸려 있는 동안은 다른 transaction이 해당 분산
트랜잭션이 변경한 data와 같은 block의 어떠한 data라도 읽거나
쓰려고 하면, 그 block에 commit되지 않은 transaction이 있다는 것을
인식하고 before image를 읽기 위해 rollback segment를 찾게 되고,
그 rollback segment에 prepared상태로 표시되어 있어 before image
읽는 것을 막기 때문에 오류가 발생하게 된다. 이 오류가 ORA-1591이
되는 것이다.
transaction이 prepared상태로 distributed lock이 걸린 상태인지는
DBA_2PC_PENDING의 status가 PREPARED인지를 확인하는 것만이
dictionary를 통해 가능한 정보이다.
[참조 2] DBA_2PC_PENDING의 정보
DBA_2PC_PENDING view의 정보는 분산 트랜잭션이 비정상 종료 되었을
때만 정보가 저장되는 것이 아니다. 앞의 [표 1]의 2 phase commit
단계마다, 수행되는 작업에 대해서 해당 view에 계속해서 정보를
변경해 가고 앞의 표의 (16), (17) 단계를 완료해야 지워지게 된다.
분산 트랜잭션이 비정상 종료시 이 view에서 해당 transaction의
상태가 COLLECTING이나 PREPARED, COMMITTED 상태로 정보가 보여지는
것은 마지막 정리 단계 수행 전에 transaction이 종료되었기 때문이다.
     non-commit point site의 경우, (10)번 단계에서 distributed lock을
걸기 전까지는 DBA_2PC_PENDING의 STATE column 값이 COLLECTING으로
나타나게 되며, (15) 단계 수행전까지는 PREPARED로 나타나고, (17)번
     수행전까지는 COMMITTED로 나타난다.
commit point site의 경우는, (11)번 수행단계까지는 이 view에 어떠한
정보도 포함하지 않으며, (12)번 수행 후 (16)번 단계를 수행하기
전까지는 COMMITTED로 STATE 값을 가지게 된다.

No commit message

Similar Messages

Maybe you are looking for