SQl Developer 3.2 Product Release Now Available

Hi,
See Data Miner forum announcement: https://forums.oracle.com/forums/ann.jspa?annID=1854
For more information about SQL Dev 3.2 in general: http://www.oracle.com/technetwork/developer-tools/sql-developer/overview/index.html
Thanks, Mark

You can use the 32 or the 64 bit versions.
But if you want to use the OCI/thick stuff, the bit level will have to match, 32 bit SQLDev with 32 bit Oracle Client with 32 bit JDK. Same goes with 64.
When you download the 64 bit dist of SQLDev for windows, you'll need to get a 64bit JDK, and make sure you have a 64 bit Oracle Client if you want to use that.
If you need more info, I wrote up more detailed instructions here
http://www.thatjeffsmith.com/archive/2012/05/getting-started-with-sql-developer-less-than-5-minutes/

Similar Messages

BI Beans 9.0.3 production is now available!!

We are pleased to announce that BI Beans 9.0.3 production is now available for download. Go to http://otn.oracle.com/products/bib/content.html for software, samples, tutorials and more.
This is the first production release of BI Beans that supports Oracle 9.2 - including the new analytic capabilities available with Analytic Workspaces.
This version of BI Beans requires JDeveloper 9.0.3.
Enjoy!
BI Beans PM

Our organization is also waiting for the 9.0.3 release of BI Beans Production. Could the BI Beans PM team give us an approximate date as to the release so that we may ensure our development resources are available at that time? It is difficult to initiate a development project when we are checking OTN daily to determine if we may proceed.

Data Miner Extension in SQL Developer 4.0 EA3 Release: EA3 Repository Migration Failure

The Data Miner extension in the SQL Developer 4.0 EA3 release fails when attempting to migrate the repository to EA3. This posting contains instructions on how to recover from this failure as well as to successful migrate the repository from EA2 to EA3. There are no problems when just installing a fresh Data Miner repository.
Sorry about the difficulty if this has caused you any problems.
Mark
Failure message displayed in log when migrating to EA3:
Error report -
ORA-06550: line 96, column 40:
PLS-00382: expression is of wrong type
ORA-06550: line 96, column 7:
PL/SQL: Statement ignored
06550. 00000 - "line %s, column %s:\n%s"
*Cause:    Usually a PL/SQL compilation error.
*Action:
Instructions on how to recover from failure and continue using original version of SQL Developer:
1) Execute the following sql as SYS in order to allow the Data Miner repository to be open for use again:
UPDATE ODMRSYS.ODMR$REPOSITORY_PROPERTIES
SET PROPERTY_STR_VALUE = 'LOADED'
WHERE PROPERTY_NAME = 'REPOSITORY_STATUS';
COMMIT;
2) During attempted migrationto EA3 failed, access priviliges to the Data Miner repository are revoked from users. In order to use Data Miner again, these grants must be reapplied. You can either use the UI guided process to accomplish this, which requires the SYS password, or you can run the usergrants.sql script, again as the SYS user. For instructions on how to run the usergrants.sql script, or any adminstrative script, review the instructions contained in the install_scripts_readme.html file. You can find this file in the SQL Developer directories created when you unzipped SQL Developer. It is located in the following relative directory: \<SQL Developer Install Directory>\sqldeveloper\dataminer\scripts.
Instructions on how to successfully migrate to EA3.
If you have already attempted to migrate to EA3 and failed, then you need to perform the recovery instructions noted above, after which you can continue with the instructions below.
If you have not yet attempted to migrate to EA3, then just following the instructions below.
1) Replace all contents the script file createxmlworkflowsbackup.sql with specification contained at the end of this posting. The file to edit can be found in the \<SQL Developer Install Directory>\sqldeveloper\dataminer\scripts directory.
2) After completing the edit to createxmlworkflowsbackup.sql, you can proceed with the UI guided migration or perform the migration using the appropriate migration script. Review the install_scripts_readme.html file in the /dataminer/scripts directory for instructions on how to perform the migration using the script. For the UI migration, simply open any user connection in your Data Miner navigator, and you will be prompted to perform the migration.
WHENEVER SQLERROR EXIT SQL.SQLCODE;
DEFINE MAX_VERSIONS = 30
EXECUTE dbms_output.put_line('Start Backup Data Miner Workflows ' || systimestamp);
DECLARE
table_cnt NUMBER;
BEGIN
SELECT count(*) INTO table_cnt FROM all_tables WHERE owner='ODMRSYS' AND table_name='ODMR$WORKFLOWS_BACKUP';
IF (table_cnt = 0) THEN
    EXECUTE IMMEDIATE '
      CREATE TABLE ODMRSYS.ODMR$WORKFLOWS_BACKUP
        USER_NAME VARCHAR2(30 CHAR) NOT NULL
      , PROJECT_ID NUMBER NOT NULL
      , PROJECT_NAME VARCHAR2(30 CHAR) NOT NULL
      , PJ_CREATION_TIME TIMESTAMP(6) NOT NULL
      , PJ_LAST_UPDATED_TIME TIMESTAMP(6)
      , PJ_COMMENTS VARCHAR2(4000 CHAR)
      , WORKFLOW_ID NUMBER NOT NULL
      , WORKFLOW_NAME VARCHAR2(30 CHAR) NOT NULL
      , WORKFLOW_DATA SYS.XMLTYPE
      , CHAIN_NAME VARCHAR2(30 CHAR)
      , RUN_MODE VARCHAR2(30 CHAR)
      , STATUS VARCHAR2(30 CHAR) NOT NULL
      , WF_CREATION_TIME TIMESTAMP(6) NOT NULL
      , WF_LAST_UPDATED_TIME TIMESTAMP(6)
      , BACKUP_TIME TIMESTAMP(6) NOT NULL
      , VERSION NUMBER NOT NULL
      , WF_COMMENTS VARCHAR2(4000 CHAR)
      , CONSTRAINT ODMR$WORKFLOWS_BACKUP_PK PRIMARY KEY
          PROJECT_ID
        , WORKFLOW_ID
        , VERSION
        ENABLE
      LOGGING
      PCTFREE 10
      INITRANS 1
      XMLTYPE COLUMN "WORKFLOW_DATA" STORE AS BASICFILE CLOB';
END IF;
END;
DECLARE
schema_old_ver VARCHAR2(30);
schema_ver   VARCHAR2(30);
patch        VARCHAR2(30);
db_ver       VARCHAR2(30);
v_storage    VARCHAR2(30);
schema_data CLOB;
v_db_11_2_0_2 NUMBER; -- db is <= 11.2.0.2?
row_cnt      NUMBER;
ver_num      NUMBER := 1;
maintaindom NUMBER;
workflow_rec ODMRSYS.ODMR$WORKFLOWS_BACKUP%ROWTYPE;
BEGIN
SELECT STORAGE_TYPE INTO v_storage FROM ALL_XML_TAB_COLS WHERE OWNER='ODMRSYS' AND TABLE_NAME='ODMR$WORKFLOWS' AND COLUMN_NAME='WORKFLOW_DATA';
if (db is >= 11.2.0.3 AND SQL Dev > 3.0) OR (db is <= 11.2.0.2 AND MAINTAIN_DOM_PATCH_INSTALLED)
    back up all workflows
end if
IF (v_storage != 'BINARY') THEN
    -- determine xml schema version
    SELECT XMLSerialize(CONTENT SCHEMA AS CLOB) INTO schema_data
    FROM DBA_XML_SCHEMAS WHERE schema_url = 'http://xmlns.oracle.com/odmr11/odmr.xsd' AND owner = 'ODMRSYS';
    maintaindom := INSTR(schema_data, 'xdb:maintainDOM="false"', 1, 1);
    -- determine database version
    SELECT version INTO db_ver FROM product_component_version WHERE product LIKE 'Oracle Database%';
    --- Check schema compatibility
    schema_old_ver := '11.2.0.1.9'; -- default value
    BEGIN
      SELECT property_str_value INTO schema_ver
      FROM "ODMRSYS"."ODMR$REPOSITORY_PROPERTIES" WHERE property_name = 'WF_VERSION';
      IF schema_old_ver = schema_ver THEN
        IF NOT (db_ver = '11.2.0.1' OR db_ver = '11.2.0.2') THEN
          dbms_output.put_line('WARNING: The backup process can not be done, The workflows need to be migrated first');
        RETURN;
        END IF;
      END IF;
    EXCEPTION WHEN NO_DATA_FOUND THEN
      schema_ver := schema_old_ver;
      dbms_output.put_line('No WF_VERSION found. Defaults to: ' || schema_old_ver);
    END;
    -- determine if MAINTAIN_DOM_PATCH_INSTALLED
    IF (INSTR(db_ver, '11.2.0.2') > 0 OR INSTR(db_ver, '11.2.0.1') > 0 OR INSTR(db_ver, '11.2.0.0') > 0) THEN
      v_db_11_2_0_2 := 1;
      BEGIN
        SELECT PROPERTY_STR_VALUE INTO patch FROM ODMRSYS.ODMR$REPOSITORY_PROPERTIES WHERE PROPERTY_NAME = 'MAINTAIN_DOM_PATCH_INSTALLED';
        patch := UPPER(patch);
      EXCEPTION WHEN NO_DATA_FOUND THEN
        patch := 'FALSE';
      END;
    ELSE
      v_db_11_2_0_2 := 0;
    END IF;
END IF;
IF (   v_storage = 'BINARY'
      OR (v_db_11_2_0_2 = 0) -- db is >= 11.2.0.3
      OR ((v_db_11_2_0_2 > 0) AND ((patch = 'TRUE') OR (maintaindom = 0))) ) THEN -- db is <= 11.2.0.2 AND (MAINTAIN_DOM_PATCH_INSTALLED OR maintaindom="true")
    SELECT count(*) INTO row_cnt FROM ODMRSYS.ODMR$WORKFLOWS_BACKUP;
    IF (row_cnt > 0) THEN
      SELECT NVL(MAX(VERSION)+1,1) INTO ver_num FROM ODMRSYS.ODMR$WORKFLOWS_BACKUP;
    END IF;
    FOR wf IN (
      SELECT
        p.USER_NAME "USER_NAME",
        p.PROJECT_ID "PROJECT_ID",
        p.PROJECT_NAME "PROJECT_NAME",
        p.CREATION_TIME "PJ_CREATION_TIME",
        p.LAST_UPDATED_TIME "PJ_LAST_UPDATED_TIME",
        p.COMMENTS "PJ_COMMENTS",
        x.WORKFLOW_ID "WORKFLOW_ID",
        x.WORKFLOW_NAME "WORKFLOW_NAME",
        xmlserialize(DOCUMENT x.WORKFLOW_DATA as CLOB indent size = 2) "WORKFLOW_DATA",
        x.CHAIN_NAME "CHAIN_NAME",
        x.RUN_MODE "RUN_MODE",
        x.STATUS "STATUS",
        x.CREATION_TIME "WF_CREATION_TIME",
        x.LAST_UPDATED_TIME "WF_LAST_UPDATED_TIME",
        x.COMMENTS "WF_COMMENTS"
      FROM ODMRSYS.ODMR$PROJECTS p, ODMRSYS.ODMR$WORKFLOWS x
      WHERE p.PROJECT_ID = x.PROJECT_ID
    LOOP
      workflow_rec.USER_NAME := wf.USER_NAME;
      workflow_rec.PROJECT_ID := wf.PROJECT_ID;
      workflow_rec.PROJECT_NAME := wf.PROJECT_NAME;
      workflow_rec.PJ_CREATION_TIME := wf.PJ_CREATION_TIME;
      workflow_rec.PJ_LAST_UPDATED_TIME := wf.PJ_LAST_UPDATED_TIME;
      workflow_rec.PJ_COMMENTS := wf.PJ_COMMENTS;
      workflow_rec.WORKFLOW_ID := wf.WORKFLOW_ID;
      workflow_rec.WORKFLOW_NAME := wf.WORKFLOW_NAME;
      workflow_rec.WORKFLOW_DATA := SYS.XMLTYPE(wf.WORKFLOW_DATA);
      workflow_rec.CHAIN_NAME := wf.CHAIN_NAME;
      workflow_rec.RUN_MODE := wf.RUN_MODE;
      workflow_rec.STATUS := wf.STATUS;
      workflow_rec.WF_CREATION_TIME := wf.WF_CREATION_TIME;
      workflow_rec.WF_LAST_UPDATED_TIME := wf.WF_LAST_UPDATED_TIME;
      workflow_rec.BACKUP_TIME := SYSTIMESTAMP;
      workflow_rec.VERSION := ver_num;
      workflow_rec.WF_COMMENTS := wf.WF_COMMENTS;
      BEGIN
        -- Output the ids (proj name, workflow name, proj id, workflow id)
        dbms_output.put_line('Backup workflow: ('||wf.PROJECT_NAME||', '||wf.WORKFLOW_NAME||', '||wf.PROJECT_ID||', '||wf.WORKFLOW_ID||')');
        INSERT INTO ODMRSYS.ODMR$WORKFLOWS_BACKUP VALUES workflow_rec;
        COMMIT;
      EXCEPTION WHEN OTHERS THEN
        dbms_output.put_line('Backup workflow failed: ('||wf.PROJECT_NAME||', '||wf.WORKFLOW_NAME||', '||wf.PROJECT_ID||', '||wf.WORKFLOW_ID||')');
      END;
    END LOOP;
END IF;
-- keep the latest 30 versions
EXECUTE IMMEDIATE 'DELETE FROM ODMRSYS.ODMR$WORKFLOWS_BACKUP WHERE VERSION <= :1' USING (ver_num - &MAX_VERSIONS);
COMMIT;
EXCEPTION WHEN OTHERS THEN
ROLLBACK;
RAISE_APPLICATION_ERROR(-20000, 'Workflow backup failed. Review install log.');
END;
EXECUTE dbms_output.put_line('End Backup Data Miner Workflows. ' || systimestamp);

823006 wrote:
5.a. XLS export of big number columns looses precision, for example a number(38) column with all digits used.
I believe excel only holds 15 digits of precision.
Edited by: 823006 on Jan 18, 2011 8:14 AMThen it would be nice if you can define the "excel type" of each column. So you can make this number a "string" in the XLS.
Edited by: user9361780 on Jan 18, 2011 9:12 AM

OraOLEDB 9.2.0.4.0 production release is available

OraOLEDB 9.2.0.4.0 production release is available for download from OTN. Broken download link issue has been fixed.
What's new in this release?
===========================
New Data Types Support
Oracle9i and later versions data types:
- TIMESTAMP
- TIMESTAMP WITH TIME ZONE
- TIMESTAMP WITH LOCAL TIME ZONE
- INTERVAL YEAR TO MONTH
- INTERVAL DAY TO SECOND
TIMESTAMP, TIMESTAMP WITH TIME ZONE, and TIMESTAMP WITH LOCAL TIME ZONE data types are mapped to OLE DB DBTYPE_DBTIMESTAMP; INTERVAL YEAR TO MONTH and INTERVAL DAY TO SECOND are to DBTYPE_STR.
OLE DB DBTYPE_DBTIMESTAMP data type does not have TIME ZONE information. For data insertion into a TIMESTAMP WITH TIME ZONE or TIMESTAMP WITH LOCAL TIME ZONE, the client's time zone setting is used. For data retrieval, TIME ZONE is dropped for TIMESTAMP WITH TIME ZONE columns, but TIME ZONE is used for TIMESTAMP WITH LOCAL TIME ZONE columns.
For TIMESTAMP, TIMESTAMP WITH TIME ZONE, and TIMESTAMP WITH LOCAL TIME ZONE, ADO consumers must specify the CursorLocation as adUseServer and use Recordset for DML operations.
Fractional second is not supported for TIMESTAMP binding with Command objects. Note that using ALTER SESSION to change time zone information will not change the time zone information in the new and existent Recordsets. Recordsets use the client's time zone setting in Operating System's Regional Options.
Supported INTERVAL Formats:
- INTERVAL YEAR TO MONTH: "(sign)years-months"
Example:
"2-3" (2 years and 3 months)
"+2-3" (2 years and 3 months)
"-2-3" (negative 2 years and 3 months)
- INTERVAL DAY TO SECOND: "(sign)days hours:minutes:seconds.fraction"
Example:
"7 10:20:30.123456"
(7 days, 10 hours, 20 minutes, and 30.123456 seconds)
"+7 10:20:30.123456"
(7 days, 10 hours, 20 minutes, and 30.123456 seconds)
"-7 10:20:30.123456"
(negative 7 days, 10 hours, 20 minutes, and 30.123456 seconds)
OraOLEDB-specific Connection String Attributes
==============================================
UseSessionFormat - specifies whether to use the default NLS session formats or let OraOLEDB override some of these formats for the duration of the session.
Valid values are 0 (FALSE) and 1 (TRUE). The default is FALSE which lets OraOLEDB override some of the default NLS session formats. If the value is TRUE, OraOLEDB uses the default NLS session formats.
Note that this connection attribute does not appear under the OLEDB registry key.
BUG FIXES (in 9.2.0.4.0)
========================
1. -2147217887 is generated when inserting data using accessor class (Bug #3114560)
2. Calls to OpenSchema leak memory (Bug #3038113)
3. Fraction gets truncated for FLOAT column when decimal separator changed to comma (Bug #1633090)
4. Returns incorrect data for LONG-RAW columns with default ChunkSize 100 bytes (Bug #3069807)
5. Failures and access violation occur on 'SELECT CASE' queries (Bug #2910141)
6. Memory leaks during connect/disconnect (Bug #2794171)
7. Oracle OLE DB Provider returns DBTYPE_STR when it should return DBTYPE_WSTR (Bug #2651518)
8. SELECT with a parameter bind of type number in WHERE clause causes ORA-1722 error (Bug #2391768)
9. Corrupts data when using multi-threaded application (Bug #2822641)
10. Does not return DBSTATUS_S_TRUNCATED appropriately (Bug #2743415)
11. Memory leaks when using "SELECT DISTINCT" and aduseclient (Bug #2626329)
12. ORA-01036 error occurs when using bind variable (Bug #2665941)
13. 'SELECT CASE' returns ORA-923: FROM keyword not found (Bug #2457001)
14. Wrong order of ADO output parameters crash appl/vb when one param is of Timestamp type (Bug #3158709)
15. ALTER SESSION SET NLS_NUMERIC_CHARACTERS = ', ' truncates float after decimal (Bug #3158709)
16. Date values cause intermittent DB_E_ERRORSOCCURRED in COM+ application (Bug #3209734)
17. OraOLEDB crashes with 800 bind parameters and PL/SQL anonymous block (Bug #2744164)
18. Oraoledbgmr!odbcsqltoorclsql crashes with COM+ under load (Bug #2730995)

Is the recommended 9.2.0.4 patchset needed for the Database Server only? Is there a patchset to upgrade the 9i Client to 9.2.0.4 also?

OO4O 9.2.0.4.8 production release is available

OO4O 9.2.0.4.8 production release is available for download on OTN.
New Features
============
New Features supported for the 32-bit In Process OLE Automation Server:
With this release, OO4O provides four new objects that enable developers to access and manipulate the new datetime and interval datatypes introduced in Oracle9i.
OO4O Objects Oracle Datatypes
OraIntervalD INTERVAL DAY TO SECOND
OraIntervalY INTERVAL YEAR TO MONTH
OraTimeStamp TIMESTAMP
TIMESTAMP WITH LOCAL TIME ZONE
OraTimeStampTZ TIMESTAMP WITH TIME ZONE
Instances of these types can be fetched from the database or passed as input or output variables to SQL statements and PL/SQL blocks, including stored procedures and functions.
These new datatypes are not supported as elements in collections such as PL/SQL Indexed Tables, VARRAYs, or Nested Tables. Please refer to the OO4O doc for more information.
Summary of problems fixed
=========================
2797039 - SIGNIFICANT DELAY IN MONITORSTART DETECTING AN ENQUEUED MESSAGE
3049591 - OOBJECT.GETATTRVALUE() RETURNS NAME OF ATTRIBUTE TO BE RETRIEVED INSTEAD VALUE
2843494 - 0040 VB APPLICATION FAILS WITH ACCESS VIOLATION
2647144 - SETTING ORACOLLECTION NOTHING CAUSE ACCESS VIOLATION
2787093 - GETFIELDCHUNK FUNCTION DOES NOT READ MORE THAN 4096 BYTES
2614824 - ACCESSING VARRAY OBJECT OF DEQUEUED MESSAGE THROWS EXCEPTION
2594695 - OFIELD::SETXMLASATTRIBUTE(TRUE) HAS NO EFFECT
2594037 - USING OFIELD::SETXMLTAGNAME RESULTS IN A OIP-04096: INVALID ADVISORY CONNECTION
2594032 - OFIELD::GETXMLTAGNAME RESULTS IN AN INVALID CHAR*
2457000 - MEMORYLEAK HAPPENS WHEN EXECUTING "ODYNASET.OPEN" AGAINST LOB ON OO4O+VC
2391180 - OO4O RETURNS OIP-4117 WHEN UPDATING FOR CASE SENSITIVE COLUMNS.
2555543 - UNNECESSARY FETCH OBSERVED IN SQL TRACE WHEN USING UPDATABLE DYNASET
2311470 - IF CREATING DYNASET "SELECT BLOB,LONGRAW FROM TAB", GPF OCCURS AT GETCHUNKBYTEEX

Is the recommended 9.2.0.4 patchset needed for the Database Server only? Is there a patchset to upgrade the 9i Client to 9.2.0.4 also?

[ANN] Oracle JDeveloper 10g production is now available for download.

It's probably worth a mention in this forum too ;-)
In case you haven't notice we have just released Oracle JDeveloper 10g production with a many new features that makes it the ideal Java tools for Oracle Application Server users.
Check it out at:
http://otn.oracle.com/products/jdev
A partial list of new features:
Visual layout editing for both JSP/HTML and Swing user interfaces.
Drag-and-Drop data-binding of business services to the user interface
Visual Struts-based page flow modeler
Declarative creation of business services based on EJB, TopLink, JavaBeans, Web Services, or Oracle ADF Business Components
Visual UML modeling with code generation
Code Auditing and Metrics
Hot-Swap Debugging
Improved code editor
XML Schema visual editor
Database development and Database modeling
One-Click deploy to Oracle Application Server, BEA Weblogic, JBoss and Tomcat
Web services development and consumption with support for WS-I
And much more.

Hi,
That is definitely a product manager - positioning question (forum ID: oalonso), so I'd recommend that you ask the same question in the SES forum. The Text team has been monitoring that forum and answering most of the posts there, so you'd probably be more likely to get your question answered.
Secure Enterprise Search
-Ron

Beta Refresh Release Now Available! Sun Cluster 3.2 Beta Program

The Sun Cluster 3.2 Release team is pleased to announce a Beta Refresh release. This release is based on our latest and greatest build of Sun Cluster 3.2, build 70, which is close to the final Revenue Release build of the product.
To apply for the Sun Cluster 3.2 Beta program, please visit:
https://feedbackprograms.sun.com/callout/default.html?callid=%7B11B4E37C-D608-433B-AF69-07F6CD714AA1%7D
or contact Eric Redmond <[email protected]>.
New Features in Sun Cluster 3.2
Ease of use
* New Sun Cluster Object Oriented Command Set
* Oracle RAC 10g improved integration and administration
* Agent configuration wizards
* Resources monitoring suspend
* Flexible private interconnect IP address scheme
Availability
* Extended flexibility for fencing protocol
* Disk path failure handling
* Quorum Server
* Cluster support for SMF services
Flexibility
* Solaris Container expanded support
* HA ZFS
* HDS TrueCopy campus cluster
* Veritas Flashsnap Fast Mirror Resynchronization 4.1 and 5.0 option support
* Multi-terabyte disk and EFI label support
* Veritas Volume Replicator 5.0 support
* Veritas Volume Manager 4.1 support on x86 platform
* Veritas Storage Foundation 5.0 File System and Volume Manager
OAMP
* Live upgrade
* Dual partition software swap (aka quantum leap)
* Optional GUI installation
* SNMP event MIB
* Command logging
* Workload system resource monitoring
Note: Veritas 5.0 features are not supported with SC 3.2 Beta.
Sun Cluster 3.2 beta supports the following Data Services
* Apache (shipped with the Solaris OS)
* DNS
* NFS V3
* Java Enterprise System 2005Q4: Application Server, Web Server, Message Queue, HADB

Without speculating on the release date of Sun Cluster 3.x or even its feature list, I would like to understand what risk Sun would take when Sun Cluster would support ZFS as a failover filesystem? Once ZFS is part of Solaris 10, I am sure customers will want to use it in clustered environments.
BTW: this means that even Veritas will have to do something about ZFS!!!
If VCS is a much better option, it would be interesting to understand what features are missing from Sun Cluster to make it really competitive.
Thanks
Hartmut

AMS Amazon Release now available for Sydney Region

Adobe Media Server availability on Amazon Web Services has been expanded. Amazon Machine image is now also available for Sydney Region
AMI ID -
ami-90e071aa
Instances Supported
m1.large, m1.xlarge, m2.xlarge, m2.2xlarge, m2.4xlarge, c1.xlarge
FMS 4.5.5 was also made available in Sydney region earlier
http://helpx.adobe.com/adobe-media-server/kb/flash-media-server-amazon-machine.html
Team AMS

Great news Mike! I've got my copy pre-ordered already ;-)
Do you know of any other similar Siebel CRM On Demand reference books that are available for purchase? From what I can tell, it's like trying to find a needle in a haystack!

Configurator 4 - final release now available

This is our shipping release of Configurator 4. It includes various bug fixes and introduces Hi-DPI support. It was just posted yesterday. Also look for the HMTL Sample Panel and the forthcoming Photoshop CC Features on Adobe Exchange.
Don't forget to submit the panels you create to Adobe Exchange. Sign up for a free producer account now and you can distribute your panels, whether you want them to be free, privately shared or even sell them.
We hope you enjoy the new Adobe Configurator 4 and can't see what you create with it.
Jonathan Ferman on behalf of The Adobe Configurator team

Hi,
Where can I find more info on the Hi-DPI support? Is there a way to include hi-res image assets to be used on retina displays?
Thanks.

Adobe Lens Profile Creator 1.0.1 Release Now Available

You can download the build at http://labs.adobe.com/downloads/lensprofile_creator.html. This build fixed several bugs found in the ALPC 1.0 release:
1) Fixed a metadata bug where the camera's sensor format factor (crop factor) was not written to the output lcp files for certain cameras, such as Samsung NX 10 for example.
2) ALPC asks the user to give up the saving the profile if the camera make EXIF contains special non-alphanumeric characters. See the issue as reported in http://forums.adobe.com/thread/650251?tstart=0.
3) Added a preference setting to ignore warning messages when batch processing multiple image sets. This is to improve the automated batch processing workflow.
If you have already created your profile, you should not worry about to go back to re-create the lens profiles using this new version. For new profiles that you want to generate, please pick up the latest release.
Thanks,
-Simon

http://www.adobe.com/downloads/updates/

Help: Developer 6.0 (Production Release) Problem

Hello
I am using the following platforms/tools:
NT4.0, Oracle 8.0.4, IIS 2.0, Developer Server 6.0, JInitiator
1.1.5.21.1, Internet Explorer 4.0, Static HTML (No cartridge)
My Database server and Forms server are residing on different
machines.
My Forms server & Web server are installed on the same machine.
I am having the following problem even though I followed all the
steps mentioned in the Forms server documentation &
troubleshooting:
The HTML page and the applet download at the startup, and the
applet starts running. But nothing else happens.
The message in the status bar of the Communicator window states
that
"Oracle JInitiator: Applet oracle.forms.engine.Main inited"
The ifsrv60 process is running @ port 9000 and the same is
mentioned in static html file.
I am attaching the messages on the Java Console and the static
html file. Please help me.
--------JAVA CONSOLE MESSAGES--------------------------
Oracle JInitiator version 1.1.5.21.1
Using JRE version 1.1.5.21o
User home directory = C:\WINNT\Profiles\Administrator
Proxy Configuration: Manual Configuration
Proxy:
http=proxy.kfupm.edu.sa:8080;https=proxy.kfupm.edu.sa:8080;ftp=pr
oxy.kfupm.edu.sa:8080
Proxy Overrides:
www.kfupm.edu.sa,proxy.kfupm.edu.sa,*www.ccse.kfupm.edu.sa,*pc-
oracle1.ri.kfupm.edu.sa
Opening http://pc-oracle1.ri.kfupm.edu.sa/web_jars/f60all.jar no
proxy
Opening http://pc-
oracle1.ri.kfupm.edu.sa/web_code/javax/swing/JInternalFrame.class
no proxy
Opening http://pc-
oracle1.ri.kfupm.edu.sa/web_code/oracle/forms/registry/Registry.d
at no proxy
Opening http://pc-
oracle1.ri.kfupm.edu.sa/web_code/oracle/forms/registry/default.da
t no proxy
------------END OF JAVA CONSOLE MESSAGES------------------
------------Static HTML--------------
<HTML>



<HEAD><TITLE>Moiz's Developer Server and Oracle
JInitiator</TITLE></HEAD>
<BODY>
<OBJECT classid="clsid:9F77a997-F0F3-11d1-9195-00C04FC990DC"
WIDTH=500
HEIGHT=500
codebase="http://pc-
oracle1.ri.kfupm.edu.sa/jinit115211.exe#Version=1,1,5,21,1">
<PARAM NAME="CODE" VALUE="oracle.forms.engine.Main" >
<PARAM NAME="CODEBASE" VALUE="/web_code/" >
<PARAM NAME="ARCHIVE" VALUE="/web_jars/f60all.jar" >
<PARAM NAME="type" VALUE="application/x-jinit-
applet;version=1.1.5.21.1">
<PARAM NAME="serverPort" VALUE="9000">
<PARAM NAME="serverArgs" VALUE="module=SEARCH_FORM.fmx
userid=moiz/moiz@oracle">
<PARAM NAME="serverApp" VALUE="default">
<COMMENT>
<EMBED type="application/x-jinit-applet;version=1.1.5.21.1"
java_CODE="oracle.forms.engine.Main"
java_CODEBASE="/web_code/"
java_ARCHIVE="/web_jars/f60all.jar"
WIDTH=500
HEIGHT=500
serverPort="9000"
serverArgs="module=SEARCH_FORM.fmx
userid=moiz/moiz@oracle"
serverApp="default"
pluginspage="http://pc-
oracle1.ri.kfupm.edu.sa/jinit_download.htm">
<NOEMBED>
</COMMENT>
</NOEMBED></EMBED>
</OBJECT>
</BODY>
</HTML>
null

If you are running NT service pack 4 the following seems to solve
this problem:
Try the patch on the DEV 6.0 server CD in the extras\sp4
directory.
Regards
Hennie
Zakaria MOURSLI (guest) wrote:
: Tullio Bettinazzi (guest) wrote:
: : Feroz A. khan (guest) wrote:
: : : mobeen (guest) wrote:
: : : : I have the same problem pls help.
: : : : applet comes up and says applet initiated but does not
: shows
: : : the
: : : : actual form.
: : : : Mohammed Moizuddin (guest) wrote:
: : : : : Errata: The message in the status bar of the
: Communicator
: : : : window
: : : : : states
: : : : : "Oracle JInitiator: Applet oracle.forms.engine.Main
: : : started"
: : : : : Please help me as I have to give my evaluation report
: this
: : : : week.
: : : : : Regards
: : : : : Moiz
: : : Salam Moiz,
: : : I think u r using Netsape 4 . Instead use 4.5 it will work
: coz
: : : the compatibility is with 4.5 .
: : I've the same problem and I tried with Navigator 4.5 and IE
: 4.01.
: : After two or three times ifweb60 uses 100% of CPU and I
should
: : reboot the system.
: I have exactly the same problem using:
: Developper 6.0
: IIS 4.0 / Internet Explorer 4.1
: Oracle 7.3
: And JINITIATOR 1.1.7.11
: I don't know if this bug concern the browser or the applet or
: the web server or the Forms Server ......
: Any Help !!!!!!!!!!
: Thanks
null

SQL Developer 3.1 Early Adopter 3 Available

Hi,
See announcement posting:
https://forums.oracle.com/forums/ann.jspa?annID=1730
Thanks, Mark

Can , sure. Advisable , not officially.
Your call...
Regards,
K.

Visual Studio 2010 Production Release Version Numbers

I uninstalled the beta and installed the production release. After letting it convert my projects, I noticed that the version numbers for the .NET assemblies appear to be 13.0.2000.0 and in the beta version they were 14.0.2000.0.
Can someone from SAP confirm the version numbers for the production release?

Hello,
You are correct. The final build is version 13. Long story due to download sizes and integration. I've updated 4 Images now both 32 and 64 bit and had no problems. Other major change is there is no connectivity to BOE Enterprise and no plans to add it.
See this [Link |Crystal Reports for Visual Studio 2010 Production Release Now Available;for more info and known issues.
Thank you
Don

ODM within Oracle SQL Developer 3.0 , no progress during Workflow creation

Hi,
I am trying to follow the instructions mentioned at http://www.oracle.com/webfolder/technetwork/tutorials/obe/db/11g/r2/prod/bidw/datamining/ODM11gR2.htm
In the "Create a Workflow and Add a Data Source" section when i try to create a new New Workflow from the menu, the Oracle SQL Developer 3.0 just shows a progress bar pop up with message "Validating and Updating Workflow". The workflow does not gets created even after 6 hours while the progress bar keeps moving. I tried it several times but no luck and hence not able to move further.
Thanks in advance for the help.

Hi,
Are you using the SQL Developer 3.0 Production Release?
Can you try again, but this time launch SQL Developer using the following file:
C:\<SQLDEVELOPER INSTALL DIRECTORY>\sqldeveloper\sqldeveloper\bin\sqldeveloper.exe
This will display a console window prior to SQL Developer UI being displayed.
There may be some unexpected exception that is being thrown.
It should display in this console window and give us more information to go on.
It sounds like you were able to create a Project ok.
Did you have any issues during the install of the repository?
Did you happen to save the log?
If so, can you paste it in this thread?
THanks, Mark

GeoRaptor 3.0 for SQL Developer 3.0 and 2.1 has now been released

Folks,
I am pleased to announce that, after 5 months of development and testing, a new release of GeoRaptor for SQL Developer 2.1 and 3.0 is now available.
GeoRaptor for SQL Developer 3 is available via the SQL Developer Update centre. GeoRaptor 3 for SQL Developer 2.1 is being made available
via a download fro the GeoRaptor website.
No release notes have been compiled as the principal developer (oops, that's me!) is currently busy doing real work for a change (another 3 weeks), earning a living
and keeping the wolves at bay. More extensive notes (with images) will be compiled when I get back. (Unless anyone is offering! See next.)
We are still looking for people to:
1. Provide translations of the English dialog menus etc.
2. Write more extensive user documentation. If you use a particular part of GeoRaptor a lot and think
you have found out all its functionality and quirks, contact us and offer to write a few pages of
documentation on it. (Open Office or Microsoft Word is fine.) Easiest way to do this is to simply
make screen captures and annotate with text.
3. Conduct beta testing.
Here are the things that are in the new release.
New functionality:
Overhaul of Validation Functionality.
1. User can specify own validation SELECT SQL as long as it returns three required columns. The SQL is thus totally editable.
2. Validation update code now allows user to associate a PL/SQL function with an error number which is applied in the UPDATE SQL.
3. UPDATE SQL can use WHERE clause of validation SELECT SQL (1) to update specific errors.
   NOTE: The generated UPDATE statement can be manually edited. It is NEVER run by GeoRaptor. To run any UPDATE, copy the statement
   to the clipboard and run in an appropriate SQL Worksheet session within SQL Developer.
4. Main validation table allows:
   a. Sorting (click on column header) and
   b. Filtering.
   c. Copying to Clipboard via right mouse click sub menu of:
      - Geometry's SDO_ELEM_INFO array constructor.
      - SDO_GEOMETRY constructor
      - Error + validation string.
   d. Access to Draw/Zoom functions which were previously buttons.
   e. Added a new right mouse click menu "Show Feature's Individual Errors" that gathers up all the errors
      it can process - along with the ring / element that is host to the error (if it can) - and displays
      them in the Attribute/Geometry tabs at the bottom of the Map Window (where "Identify" places its results).
      The power of this will be evident to all those who have wanted a way of stepping through errors in a geometry.
   f. Selected rows can now be deleted (select rows: press <DELETE> key or right mouse click>Delete).
   g. Table now has only one primary key column, and has a separate error column holding the actual error code.
   h. Right mouse click men added to table menu to display description of error in the new column (drawn from Oracle documentation)
   i. Optimisations added to improve performance for large error lists.
5. Functionality now has its own validation layer that is automatically added to the correct view.
   Access to layer properties via button on validation dialog or via normal right mouse click in view/layer tree.
Improved Rendering Options.
1. Linestring colour can now be random or drawn from column in database (as per Fill and Point colouring)
2. Marking of SDO_GEOMETRY objects overhauled.
   - Ability to mark or LABEL vertices/points of all SDO_GEOMETRY types with coordinate identifier and
     option {X,Y} location. Access is via Labelling tab in layer>properties. Thus, coordinate 25 of a linestring
     could be shown as: <25> or {x,y} or <25> {x,y}
   - There is a nice "stacked" option where the coordinate {x,y} can be written one line below the id.
   - For linestrings and polygons the <id> {x,y} label can be oriented to the angle between the vectors or
     edges that come in, and go out of, a vertex. Access is via "Orient" tick box in Labelling tab.
   - Uses Tools>Preferences>GeoRaptor>Visualisation>SDO_ORDINATE_ARRAY bracket around x,y string.
3. Start point of linestring/polygon and all other vertices can be marked with user selectable point marker
   rather than previously fixed markers.
4. Can now set a NULL point marker by selecting "None" for point marker style pulldown menu.
5. Positioning of the arrow for linestring/polygons has extra options:
   * NONE
   * START    - All segments of a line have the arrow positioned at the start
   * MIDDLE   - All segments of a line have the arrow positioning in the middle.
   * END      - All segments of a line have the arrow positioning in the END.
   * END_ONLY - Only the last segment has an arrow and at its end.
ScaleBar.
1. A new graphic ScaleBar option has been added for the map of each view.
   For geographic/geodetic SRIDs distances are currently shown in meters;
   For all SRIDs an attempt is made to "adapt" the scaleBar units depending
   on the zoom level. So, if you zoom right in you might get the distance shown
   as mm, and as you zoom out, cm/m/km as appropriate.
2. As the scaleBar is drawn, a 1:<DEMONINATOR> style MapScale value is written
   to the map's right most status bar element.
3. ScaleBar and MapScale can be turned off/on in View>Properties right mouse
   click menu.
Export Capabilities.
1. The ability to export a selection from a result set table (ie result of
   executing ad-hoc SQL SELECT statement to GML, KML, SHP/TAB (TAB file
   adds TAB file "wrapper" over SHP) has been added.
2. Ability to export table/view/materialised view to GML, KML, SHP/TAB also
   added. If no attributes are selected when exporting to a SHP/TAB file, GeoRaptor
   automatically adds a field that holds a unique row number.
3. When exporting to KML:
   * one can optionally export attributes.
   * Web sensitive characters < > & etc for KML export are replaced with > < & etc.
   * If a column in the SELECTION or table/view/Mview equals "name" then its value is
     written to the KML tag <name> and not to the list of associated attributes.
     - Similarly for "description" -> <description> AND "styleUrl" -> <styleUrl>
4. When exporting to GML one can optionally export attributes in FME or OGR "flavour".
5. Exporting Measured SDO_GEOMETRY objects to SHP not supported until missing functionality
   in GeoTools is corrected (working with GeoTools community to fix).
6. Writing PRJ and MapInfo CoordSys is done by pasting a string into appropriate export dialog box.
   Last value pasted is remembered between sessions which is useful for users who work with a single SRID.
7. Export directory is remembered between sessions in case a user uses a standard export directory.
8. Result sets containing MDSYS.SDO_POINT and/or MDSYS.VERTEX_TYPE can also be written to GML/KML/SHP/TAB.
   Example:
   SELECT a.geom.sdo_point as point
     FROM (SELECT sdo_geometry(2002,null,sdo_point_type(1,2,null),sdo_elem_info_array(1,2,1),sdo_ordinate_array(1,1,2,2)) as geom
             FROM DUAL) a;
   SELECT mdsys.vertex_type(a.x,a.y,a.z,a.w,a.v5,a.v6,a.v7,a.v8,a.v9,a.v10,a.v11,a.id) as vertex
     FROM TABLE(mdsys.sdo_util.getVertices(mdsys.sdo_geometry(2002,null,null,sdo_elem_info_array(1,2,1),sdo_ordinate_array(1,1,2,2)))) a;
9. A dialog appears at the end of each export which details (eg total) what was exported when the exported recordset/table contains more
   than on shape type. For example, if you export only points eg 2001/3001 from a table that also contains multipoints eg 2005/3005 then
   the number of points exported, and multipoints skipped will be displayed.
10. SHP/TAB export is "transactional". If you set the commit interval to 100 then only 100 records are held in memory before writing.
    However, this does not currently apply to the associated DBASE records.
11. SHP/TAB export supports dBase III, dBase III + Memo, dBase IV and dBase IV + Memo.
    Note: Memo allows text columns > 255 characters to be exported. Non-Memo formats do not and any varchar2 columns will be truncated
    to 255 chars. Some GIS packages support MEMO eg Manifold GIS, some do not.
12. Note. GeoRaptor does not ensure that the SRID of SDO_GEOMETRY data exported to KML is in the correct Google Projection.
    Please read the Oracle documentation on how to project your data is this is necessary. An example is:
    SELECT OBJECTID,
           CODIGO as name,
           NOME as description,
           MI_STYLE,
           SDO_CS.TRANSFORM(shape,'USE_SPHERICAL',4055) as shape
      FROM MUB.REGIONAL;
13. NOTE: The SHP exporter uses the Java Topology Suite (JTS) to convert from SDO_GEOMETRY to the ESRI Shape format. JTS does not handle
    circular curves in SDO_GEOMETRY objects you must "stroke" them using sdo_util.arc_densify(). See the Oracle documentation on how
    to use this.
Miscellaneous.
1. Selection View - Measurement has been modified so that the final result only shows those geometry
   types that were actually measured.
2. In Layer Properties the Miscellaneous tab has been removed because the only elements in it were the
   Geometry Output options which have now been replaced by the new GML/KML/etc export capabilities.
3. Shapefile import's user entered tablename now checked for Oracle naming convention compliance.
4. Identify based on SDO_NN has been removed from GeoRaptor given the myriad problems that it seems to create across versions
   and partitioned/non-partitioned tables. Instead SDO_WITHIN_DISTANCE is now used with the actual search distance (see circle
   in map display): everything within that distance is returned.
5. Displaying/Not displaying embedded sdo_point in line/polygon (Jamie Keene), is now controlled by
   a preference.
6. New View Menu options to switch all layers on/off
7. Tools/Preferences/GeoRaptor layout has been improved.
8. If Identify is called on a geometry a new right mouse click menu entry has been added called "Mark" which
   has two sub-menus called ID and ID(X,Y) that will add the labeling to the selected geometry independently of
   what the layer is set to being.
9. Two new methods for rendering an SDO_GEOMETRY object in a table or SQL recordset have been added: a) Show geometry as ICON
   and b) Show geometry as THUMBNAIL. When the latter is chosen, the actual geometry is shown in an image _inside_ the row/column cell it occupies.
   In addition, the existing textual methods for visualisation: WKT, KML, GML etc have been collected together with ICON and THUMBNAIL in a new
   right mouse click menu.
10. Tables/Views/MViews without spatial indexes can now be added to a Spatial View. To stop large tables from killing rendering, a new preference
    has been added "Table Count Limit" (default 1,000) which controls how many geometry records can be displayed. A table without a spatial
    index will have its layer name rendered in Italics and will write a warning message in red to the status bar for each redraw. Adding an index
    which the layer exists will be recognised by GeoRaptor during drawing and switch the layer across to normal rendering.
Some Bug Fixes.
* Error in manage metadata related to getting metadata across all schemas
* Bug with no display of rowid in Identify results fixed;
* Some fixes relating to where clause application in geometry validation.
* Fixes bug with scrollbars on view/layer tree not working.
* Problem with the spatial networks fixed. Actions for spatial networks can now only be done in the
schema of the current user, as it could happen that a user opens the tree for another schema that
has the same network as in the user's schema. Dropping a drops only the network of the current connected user.
* Recordset "find sdo_geometry cell" code has been modified so that it now appears only if a suitable geometry object is
in a recordset. Please note that there is a bug in SQL Developer (2.1 and 3.0) that causes SQL Developer to not
register a change in selection from a single cell to a whole row when one left clicks at the left-most "row number"
column that is not part of the SELECT statements user columns, as a short cut to selecting a whole row. It appears
that this is a SQL Developer bug so nothing can be done about it until it is fixed. To select a whole row, select all
cells in the row.
* Copy to clipboard of SDO_GEOMETRY with M and Z values forgot has extraneous "," at the end.
* Column based colouring of markers fixed
* Bunch of performance improvements.
* Plus (happily) others that I can't remember!If you find any bugs register a bug report at our website.
If you want to help with testing, contact us at our website.
My thanks for help in this release to:
1. John O'Toole
2. Holger Labe
3. Sandro Costa
4. Marco Giana
5. Luc van Linden
6. Pieter Minnaar
7. Warwick Wilson
8. Jody Garnett (GeoTools bug issues)
Finally, when at the Washington User Conference I explained the willingness of the GeoRaptor Team to work
for some sort of integration of our "product" with the new Spatial extension that has just been released in SQL
Developer 3.0. Nothing much has come of that initial contact and I hope more will come of it.
In the end, it is you, the real users who should and will decide the way forward. If you have ideas, wishes etc,
please contact the GeoRaptor team via our SourceForge website, or start a "wishlist" thread on this forum
expressing ideas for future functionality and integration opportunities.
regards
Simon
Edited by: sgreener on Jun 12, 2011 2:15 PM

Thank you for this.
I have been messing around with this last few days, and i really love the feature to pinpoint the validation errors on map.
I has always been so annoying to try pinpoint these errors using some other GIS software while doing your sql.
I have stumbled to few bugs:
1. In "Validate geometry column" dialog checking option "Use DimInfo" actually still uses value entered in tolerance text box.
I found this because in my language settings , is the decimal operators
2. In "Validate geometry column" dialog textboxs showing sql, doesn't always show everything from long lines of text (clipping text from right)
3. In "Validate geometry column" dialog the "Create Update SQL" has few bugs:
- if you have selected multiple rows from results and check the "Use Selected Geometries" the generated IN-clause in SQL with have same rowid (rowid for first selected result) for all entries
Also the other generated IN clause in WHERE-clause is missing separator if you select more than one corrective function
4. "Validate geometry column" dialog stays annoyingly top most when using "Create Update SQL" dialog

SQl Developer 3.2 Product Release Now Available

Similar Messages

Maybe you are looking for