Headstart patch 13

Iam trying to download patch13 from otn but is giving bad url.there seems to be a problem in the path of patch13 zip file

In fact i am not able to download anything from OTN for last 3 days.

Similar Messages

Headstart Patch 6.5.2.3

I have just installed patch 6.5.2.3 and am going through and re-creating my CAPIs using the utility 'Create CAPI Definition'.
I have a table where I have set Complete=No on one of the columns. It appears that this column is now being included when the utility creates the CAPI, which causes errors when I try to compile it as the column doesn't exist within the table in the database.
Is this a new bug, or is there something else I should be setting?
Also, at the end of each CAPI's package body there is now an 'end;' statement, which never used to get created. We now have to go through and comment this line out of every CAPI in order to get them to create. Any other way around this?
Thanks in advance,
Kim.

I was running just the base version of Headstart until yesterday, when I applied all 3 patches at once. On the base version this column wasn't being included in the CAPI, and now it is, so I guess the change could've come about in any of the patches.
The name of my table is reg_photos, and the column that has Complete=No is large_image.
The specific areas of the CAPI where it's included and which cause compilation errors are:
There's public cursors at the start of the package where the column is being selected:
-- public cursors
-- cursor to select one particular row
cursor c_rpho
( b_project_code in varchar2
, b_photo_no in number
) is
select rpho.rowid the_rowid
, rpho.project_code
, rpho.photo_no
, rpho.photo_type
, rpho.photo_date
, rpho.small_image
, rpho.large_image
, rpho.created_by
, rpho.creation_date
, rpho.last_updated_by
, rpho.last_update_date
from reg_photos rpho
where rpho.project_code = b_project_code
and rpho.photo_no = b_photo_no
-- cursor to select all rows
cursor c_rpho_all
is
select rpho.rowid the_rowid
, rpho.project_code
, rpho.photo_no
, rpho.photo_type
, rpho.photo_date
, rpho.small_image
, rpho.large_image
, rpho.created_by
, rpho.creation_date
, rpho.last_updated_by
, rpho.last_update_date
from reg_photos rpho
It's also included in function get_char_value but this isn't causing a compilation error:
elsif upper(p_column_name) = 'LARGE_IMAGE'
then
return l_row.large_image;
And also in procedure validate_row:
g_current_ind.large_image := true;
I guess it's easy enough to go in and comment all the references out, but I would've thought that columns of this nature should not be included in the CAPI in the first place?
Thanks,
Kim.

Headstart patch level vs. Repository version

What is the highest version(patch level) of Headstart that we can go to without changing our Repository version? We are currently at Repository version 4.0.12.80.6.

Hi Randy,
No not really, but as patch level 20 is the highest on sapgui 6.40, i would guess that it is a 6.20 gui...
On the other hand highest patchlevel on 6.20 gui is 64, so it is a really old installation....
You should ask them to click on the icon in the upper left corner of the saplogon / saplgpad screen and then select "About SAP Logon", a window will tell the sapgui version and patchlevel...
Regards
Rolf

Identification of headstart patch level

Hi
I inherited Headstart 5.x and Designer 6 repository, that I am supposed to migrate to 6i repository. Headstart migration guide states that Headstart 5.x must be at Patch level 11 and 12. I have media for patches 11 and 12, but I don't know if I should apply those patches or not i.e. how do I identify on what patch Headstart is.
Another question.
I do not have 5.x client installation. Since the old repository is already there, how do I install only the client without affecting the repository?
Regards
George

Dear All,
many thanks for your Replies.
As I see it now, there is no way to get this Information "out-of-the -Box".
I made copies of every old EXE Folder, so I took this Dates for the Kernel Change Day.
So I pay my penny and will write the next changes of the Kernel Patch into a Spread Sheet to keep this Informations.
Again many thanks to All
Peter

Designer 6.0 = 6i still using Headstart 2.1.2 patch 10 possible?

My client are upgrading Designer and we have som questions.
This is installed:
Designer Repository installed in 7.3.4.X
Designer 6.0 patch 5
Developer 6.0 patch 7
Discoverer 3.1.X
Headstart 2.1.2 with patch 10
PC Windows NT4
Application (190 forms, 60 reports, 40 discoverer) runs in database 8i 8.1.7 and the database is recently upgraded from 7.3.4.X.
We have developed Reports outside Designer.
We want to upgrade as far as we can with client/server support in Forms but also having the option to use webforms later.
Right now we want to upgrade to:
Designer 6 rel 4 and in database 8i
Developer 6i patch 5
Discoverer 4.1.37
IAS 1.2.2.2a (only Discoverer services)
I have read information on OTN but I did not get any answers.
Questions:
1. Can we upgrade Designer to 6i without Headstart patches and without too much problem?
What problems can we expect? I heard about LOV and record indicator changes.
2. If we have to use Headstart patches, then patch 11 to 13 is of interest that is available on OTN, is this a working solution and how much work does this imply? Our application is in production and almost a 24/7 business.
Thanks
Gustavo Forsberg
email: [email protected]
homepage: www.oraclecp.com

Hello everybody,
here's the script for width corrections of poplists, checkboxes and buttons:
declare
l_update BOOLEAN := TRUE; --SET FALSE IF LOG ONLY
l_display_width_new NUMBER := 0;
cursor items is
select modul.short_name modulename,
modul.name "modulename descr",
mco.name block_name,
'bound item' bound_type,
item.id,
item.name,
item.prompt,
item.display_type,
item.display_flag,
item.display_width,
item.display_height
from ci_general_modules modul,
ci_module_components mco,
ci_module_detail_table_usages mco_detail,
ci_items item
Where mco.general_module_reference = modul.id
and mco_detail.pac_reference = modul.id
and item.pac_reference = modul.id
and item.module_unit_reference = mco.id
and item.detail_table_usage_reference = mco_detail.id
and item.display_type IN ('CHECK BOX','POP-LIST','BUTTON')
-- test:
-- and modul.short_name IN ('module_name')
-- and mco.name = 'module_component_name'
-- and item.name = 'item_name'
union
select modul.short_name modulename,
modul.name "modulename descr",
mco.name block_name,
'unbound item' bound_type,
unbound_item.id,
unbound_item.name,
unbound_item.prompt,
unbound_item.display_type,
unbound_item.display_flag,
unbound_item.display_width,
unbound_item.display_height
from ci_general_modules modul,
ci_module_components mco,
ci_unbound_items unbound_item
Where mco.general_module_reference = modul.id
and unbound_item.module_unit_reference = mco.id
and unbound_item.display_type IN ('CHECK BOX','POP-LIST','BUTTON')
-- test:
-- and modul.short_name IN ('module_name')
-- and mco.name = 'module_component_name'
-- and item.name = 'item_name'
order by 1,2,3,5;
begin
dbms_output.put_line(RPAD('Module',10)||RPAD('item',25)||RPAD('Prompt',20)||
RPAD('disptype',15)||
RPAD('before',6)||
RPAD('after',6)||
RPAD('disp?',10));
for item in items loop
IF item.display_type = 'POP-LIST' THEN
l_display_width_new := FLOOR(item.display_width/2);
--IF YOU WANT LESS THAN 4, CHANGE PREF PLSIWD AFTER MIGRATION
--OTHERWISE WIDTH = l_display_width_new + PLSIWD (default 4)
IF l_display_width_new < 4 THEN
l_display_width_new := 4;
END IF;
if l_update = TRUE THEN
update ci_items
set display_width = l_display_width_new
where id = item.id;
end if;
ELSIF item.display_type = 'CHECK BOX' THEN
l_display_width_new := FLOOR(item.display_width * (7/10));
if l_update = TRUE THEN
update ci_items
set display_width = l_display_width_new
where id = item.id;
end if;
ELSIF item.display_type = 'BUTTON' THEN
l_display_width_new := FLOOR(item.display_width * (7/10));
if l_update = TRUE THEN
update ci_items
set display_width = l_display_width_new
where id = item.id;
end if;
END IF;
dbms_output.put_line(RPAD(item.modulename,10)||
RPAD(item.name,25)||
RPAD(NVL(item.prompt,'(NULL)'),20)||
RPAD(item.display_type,15)||
RPAD(item.display_width,6)||
RPAD(l_display_width_new,6)||
RPAD(item.display_flag,10));
end loop;
end;
Note: we found poplist width 4 problem after the script was commited, I have added the correct code. This script corrects most of the problems but it depends on you layout. If you have used PLSQL for layout changes this script might not help. Don't forget BLKUTT and GRPUTT preferences that you may have to change.
Good luck!
Regards
Gustavo Forsberg
www.oraclecp.com

ANNOUNCEMENT: Headstart Utilities Patch 6.5.2.3 now available on Supplement Option!

All,
Subscribers of the Supplement Option can now download Headstart Patch 6.5.2.3 and Headstart for Apps patch 6.5.2.3
from My Oracle, using the iDevelopment Accelerators link in the Supplement Offering portlet.
The main purpose of this patch is to improve the performance of the CDM RuleFrame engine
when large transactions are involved.
During development and testing of this patch the following improvements of the CDM RuleFrame engine
were measured on an Windows 2000 laptop with RDBMS 8.1.7.1.1.
- 100 DML statements, 3 Business Rules per statement performance improved from 1.45 sec to 1.05 sec (28%)
- 500 DML statements, 3 Business Rules per statement performance improved from 23.760 sec to 8.48 sec (64%)
- 1000 DML statements, 3 Business Rules per statement performance improved from 78.79 sec to 19.260 sec (76%)
- 2000 DML statements, 3 Business Rules per statement performance improved from above 300 sec to 48.22 sec (83%)
- 5000 DML statements, 3 Business Rules per statement performance improved from ??? to 143.41 sec
It evolves that the RuleFrame engine takes up more time for larger transactions now in a rather linear way.
This means that within 15 minutes more than 100.000 business rules can be validated
on a small windows 2000 laptop.
Besides this performance improvement, the patch also implements the following enhancements to CDM RuleFrame:
- The utility 'Create CAPI Custom Service' makes it possible to include a CAPI Custom Service
(that is, your own package or function) in more than one CAPI
- The utility 'Create VAPI Definition' can now also create VAPI's for subtypes (controlled by new utility parameter)
Furthermore, several Utilities bugs have been fixed in this patch. See the readme in the patch for more details.
If you don't have the Supplement Option, contact your local Oracle Consulting representative.
For more information, read the original announcement of the Supplement Option in this forum at
Re: Archiving the data .
kind regards,
The Headstart Team.

I was running just the base version of Headstart until yesterday, when I applied all 3 patches at once. On the base version this column wasn't being included in the CAPI, and now it is, so I guess the change could've come about in any of the patches.
The name of my table is reg_photos, and the column that has Complete=No is large_image.
The specific areas of the CAPI where it's included and which cause compilation errors are:
There's public cursors at the start of the package where the column is being selected:
-- public cursors
-- cursor to select one particular row
cursor c_rpho
( b_project_code in varchar2
, b_photo_no in number
) is
select rpho.rowid the_rowid
, rpho.project_code
, rpho.photo_no
, rpho.photo_type
, rpho.photo_date
, rpho.small_image
, rpho.large_image
, rpho.created_by
, rpho.creation_date
, rpho.last_updated_by
, rpho.last_update_date
from reg_photos rpho
where rpho.project_code = b_project_code
and rpho.photo_no = b_photo_no
-- cursor to select all rows
cursor c_rpho_all
is
select rpho.rowid the_rowid
, rpho.project_code
, rpho.photo_no
, rpho.photo_type
, rpho.photo_date
, rpho.small_image
, rpho.large_image
, rpho.created_by
, rpho.creation_date
, rpho.last_updated_by
, rpho.last_update_date
from reg_photos rpho
It's also included in function get_char_value but this isn't causing a compilation error:
elsif upper(p_column_name) = 'LARGE_IMAGE'
then
return l_row.large_image;
And also in procedure validate_row:
g_current_ind.large_image := true;
I guess it's easy enough to go in and comment all the references out, but I would've thought that columns of this nature should not be included in the CAPI in the first place?
Thanks,
Kim.

I: Patch 6.5.3.1 for 9i available via Supplement Option

On headstart patch 6.5.3.0 (patch version ONLY for Oracle 9i Forms), there is a bug introduced in library qmslib65.pll
How to reproduce
================
- Start the headstart demo
- From the menu open form Forms --> Project Business Rules
- Press F8 (execute query)
- Now you see project 1, without detail records(no employees)
- Click on the item 'Employee' (first empty record)
- Click on the item 'Name' of the Project in the master
- Now message 'FRM-40202 Field must be entered' appears
Location of the problem
=======================
QMSLIB65.pll qms$context package body
contains the following code:
. -- fix 6.5.3.0
. if get_record_property(name_in('system.cursor_record')
. ,name_in('system.cursor_block'),STATUS) = 'NEW'
. then
. set_record_property(name_in('system.cursor_record')
. ,name_in('system.cursor_block'),STATUS,INSERT_STATUS);
. end if;
. -- end fix 6.5.3.0
This piece of code should be deleted completely
Fix
===
This problem has been fixed in patch 6.5.3.1 for Headstart for Oracle 9i Forms. This patch is downloadable from the Supplement Option web site.
Kind Regards, Marc Vahsen
Headstart Team

I think I've found a bug in this release: If you have an LOV defined on a report parameter (with value and description), the when-validate-item trigger of the field will validate the description against the LOV. It adds the following code to the validation query: ||l_where_and || l_description_column || ' = ' || '''' || name_in (qms0012f.get_param_description_item(p_block_name))||''''
Th descriptor column in this case is the alias (= "description"). However, you cannot use column aliases in a where-clause. This will never work!!
Is there a fix for this problem?

Problem with Headstart Multi-Select LOV

Hi,
I'm working on a few forms which should include a Multi-Select
LOV. Now here's the problem: One MSEL doesn't close; you can
select record(s), the LOV returns them, but doesn't disappear.
Clicking Cancel doesn't help.
Another MSEL-problem in another form: if you click Select All,
this selection isn't visible in the MSEL. He returns all of the
records, but it looks like he only selected one. Working with
CTRL to select more than one record doesn't work either. This
one closes fine.
As you know I have to include module component
QMS_MSEL_LOV_BUTTONS (which includes all button-functionality),
and then it should work, but it doesn't.
We've checked all the properties and they seem to be correct. It
isn't the first time we encountered these problems. We always
rebuilt the MSEL LOV, but it doesn't help this time.
Has anyone got an idea what's causing this problem.
P.S. There are also MSEL LOV's which operate just fine, without
any problems; only these two are doing strange things.
Thx,
Wouter

Workaround provided by Lauri Boyd seems to have worked:
A bug (#1985903) was introduced in Forms 6.0.8.13.0 and later which affected Headstart. This was fixed in Headstart patch 6.5.2.1 which is available through the Supplement Option.
Description
===========
1. When using a multi-select LOV (which is displayed in a modal dialog
window), you select the records you want, press OK, and the application exits.
2. When using a shuttle control to move records from left to right or vice
versa, you select the records you want, press '>' to move them, and the
application exits.
This occurs in Forms 6.0.8.13.0 and 6.0.8.14.1. It did NOT occur in prior
releases. This is some kind of forms bug.
Workaround
==========
For some reason the call to procedure renumber in qms$msel.process_records
causes the application to exit. If you copy the code from renumber to all the
places from which it is called, it works fine.
- open qmslib65.pll in Form Builder
- open package body qms$msel
- find procedure process_records and define a local variable l_recno of type
number.
- find local procedure renumber and copy the body of this procedure
(everything
after 'begin' and before 'exception').
- replace each call to 'renumber;' with the copied code.
Regards,
Lauri

Is Headstart 6i compatible with all Designer 6i versions? Where to download?

We consider upgrading from Designer 6.0 / Headstart patch 12.4
to Designer 6i / Headstart 6i, as we are now migrating from a
7.3.4 db to 8.1.7 and from Win98 to Win2000.
I have seen documentation on migration issues from Designer 6.0
to 6i rel.2, and from Headstart to patch 13. But I understand
that with introduction of Headstart 6i, patch 13 is no longer
supported.
1. I assume that Headstart 6i could work with all Des.6i-
versions, is that right?
2. I have found the place to download patch 13, but where can I
download Headstart 6i ???

Headstart 6i is compatible with all Designer 6i versions.
However, we have found one odd quirk with Headstart 6i and Forms
6i versions 6.0.13 and higher.
Description ===========
1. When using a multi-select LOV (which is displayed in a modal
dialog window), you select the records you want, press OK, and
the application exits.
2. When using a shuttle control to move records from left to
right or vice versa, you select the records you want, press '>'
to move them, and the application exits. This occurs in Forms
6.0.8.13.0 and higher. It did NOT occur in prior releases. This
is some kind of forms bug.
Workaround ==========
For some reason the call to procedure 'renumber' in
qms$msel.process_records in qmslib65.pll causes the application
to exit. If you copy the code from renumber to all the places
from which it is called, it works fine.

NL Translation Headstart 6.5.3.1 for Designer9i available

All,
The translation of headstart 6.5.3.1 for designer 9i is available through the supplement option "iDevelopment Accelerators" (http://cso.oracle.com).
The zip is located in subfolder Headstart Oracle Designer -> Customizations & Extensions.
Kind regards,
Marc Vahsen
Headstart Team

Available now. I just checked the Headstart Supplement Option portal and downloaded the following:
Headstart Patch 6.5.3.0 for 9i:
***NEW*** Full installation set of Headstart 6.5.3.0 for 9i, to be used with Designer 9i
Headstart Patch 6.5.3.0 for 6i:
***NEW*** Patch 6.5.3.0 of Headstart 6i, to be used with Designer 6i. To be installed on top of Headstart patch 6.5.2.3

Headstart

I installed oracle designer 6.0 for NT. I also installed the Headstart patch which supposedly works with designer 6.0. However, when I try to log on to the Headstart demo application, it comes back with FRM-40733, FRM-40735 and ora-03114 messageS. The database I am using is 8.1.5.
I have noticed that the ofg libraries available in the cgenf60/admin directory for designer 6.0 have been compiled with Forms 5. Does that have anything to do with it or is it the fact that I am using 8.1.5 Database

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Sandra Muller, Headstart Team, Oracle:
Can you give more details about your situation? Which patches of Headstart have you installed (10, 11, 12?) and did you apply the workaround for using Headstart with Oracle 8.1.5 on NT? (not valid for patch 12!) When exactly do you get these messages (when you try to do what, with which user)? What are the texts that go with FRM-40733, FRM-40735 and ORA-03114?
By the way, the bug that caused the problems on Oracle 8.1.5 for NT is solved in Oracle 8.1.6. You can use Designer 6.0 with Oracle 8.1.6 if you install Designer patch set 4.
regards,
Sandra Muller<HR></BLOCKQUOTE>
The headstart patch I used is 10 which I downloaded from OTN. The user I used was Hsdemo which I created. I used the server install form to install the demo application under this user.
By the way I installed Oracle 8.1.6 and the problem disappeared.
Is patch set 4 available for downloading from OTN or do I have to order it from Oracle?
Thanks for the reply.
null

Headstart MAtrix

Hi all,
Metalink invited me to ask you if the following matrix is right:
0. Headstart 6.5.3.1
1. Highest certify version for DB? Oracle 9.2.0.5
2. Highest certify version for forms? Forms 9i Patch 3 + Patch 3306045
3. Highest certify version for reports? Reports 9i Patch 3 + Patch 3306045
4. Highest certify version for designer? Designer 9.0.2.8
5. Highest certify version for iAS? iAS 9.0.2.1
6. Dependencies?
The combination 1, 2 ,3 , 4 and 5 is a certified combination.
Action:
I would like also to know if the following is also certified:
0. Designer 9.0.2.4
1. Forms 9i Patch 3 + Patch 3306045
Forms 9i Patch 2 + Patch XXXXXXX
Forms 9i Patch 1 + Patch XXXXXXX
(if other, please can you specify which one?)
2. Reports 9i Patch 3 + Patch 3306045
Reports 9i Patch 2 + Patch XXXXXXX
Reports 9i Patch 1 + Patch XXXXXXX
(if other, please can you specify which one?)
3. Oracle 9.2.0.5
Oracle 9.2.0.4
(if other, please can you specify which one?)
4. iAS 9.0.2.1
(if other, please can you specify which one?)
5. Dependencies.
Thanks in advance.

Hi Lauri,
We will be running the headstart application instance on oracle 9i. Does this patch for Oracle 9i relate to the compliation of a hst package function/procedure which has a mismatch of parameters with its default value, '' in the spec and 'null' in the body? I just made them both the same 'null', is this correct?
Regards,
Ray.
Headstart 6i is compatible with
Forms 6i
Designer 6i, release 2 or higher
Oracle 8i
Oracle 9i (with a Headstart patch)
Regards,
Lauri

Designer6i Rel4.9 and Headstart 6.5

Hi,
we are currently using Headstart 6.5 when we generate forms from designer6i rel.2. We are also using Designer Web Assistant.
Now we are going to upgrade designer to release 4.9 (or 4.6). What Headstart paches do we need to install (if any)?
Regards, Timo

Hi,
When using designer 6i, use the last headstart patch for this version: Headstart 6.5.3.0 for designer 6i.
This patch can be downloaded (if you are subscribed) from http://cso.oracle.com
Hope this helps,
Marc Vahsen
Headstart Team

Release date Designer Headstart 10g

Is there a date on which the headstart for Designer 10g will be available?
If it is still pending, is there a document on what has to be changed to the headstart for designer 9i version (6.5.3.2) to make it work?
Regards,
Mark

Hi,
This is what i found today on the Supplement Option Website:
Oracle Consulting has tested Headstart 9i patch 6.5.3.2 in combination with Oracle Designer 10g, Oracle Forms 10g and the Oracle 10g Application Server. During this test no issues related to Headstart came up. Therefore Headstart patch 6.5.3.2 is certified for use with the components of the 10g toolstack mentioned above.
Regards,
Michiel Jonkers

Availability of Headstart 6.5.3 for Designer 9i?

We have purchased Oracle iDevelopment Accelerators for a green-field bespoke system we are building using Designer, Forms and iAS. We would like to use the following product versions:
Oracle Forms 9i
Oracle Designer 9i
Oracle 9iAS Release 2
Oracle Enterprise Server 9.0.2.1
I currently have version 6.5.0.1 of Accelerators but see from the forums that version 6.5.3 is to be used with Designer 9i - expected to be released at end of October. Can you please tell me if 6.5.3 is now available? Will this version then be suitable for the combination of products listed above?
Your help is very much appreciated.
Thanks,
Peter

Available now. I just checked the Headstart Supplement Option portal and downloaded the following:
Headstart Patch 6.5.3.0 for 9i:
***NEW*** Full installation set of Headstart 6.5.3.0 for 9i, to be used with Designer 9i
Headstart Patch 6.5.3.0 for 6i:
***NEW*** Patch 6.5.3.0 of Headstart 6i, to be used with Designer 6i. To be installed on top of Headstart patch 6.5.2.3

Headstart patch 13

Similar Messages

Maybe you are looking for