Macbook (IOS) x Uso do EBS (JAVA)

Dúvidas e discussão sobre Oracle EBS Funcional. Setup, processos, configurações, módulos, dicas, etc
Responder
archive
Rank: OraSauro
Rank: OraSauro
Mensagens: 595
Registrado em: Sex, 02 Dez 2016 7:31 am

Recentemente tive uma atualização automática do IOs de meu macbook e após isto não consegui mais usar o EBS por causa de uma atualização do JAVA. Gostaria de saber se mais alguém esta tendo o mesmo problema e se já encontrou alguma alternativa (um java compatível)

Obrigado a todos.
archive
Rank: OraSauro
Rank: OraSauro
Mensagens: 595
Registrado em: Sex, 02 Dez 2016 7:31 am

Tive o mesmo problema com o meu. Mas é um problema do JAVA que dá pra solucionar.
Seguinte:
1 - Abra Preferência de Sistemas na maça do menu suspenso;
2 - Na opção Outros, acessar JAVA; Isso irá abrir automaticamente o Painel de Controle do JAVA;
3 - Clique no botão JAVA;
4 - Clique no botão Exibir;
5 - Inclua o seguinte comando em Parâmetros do RUNTIME: -Djava.vendor="Sun Microsystems Inc."
6 - Clique em OK;
7 - Clique em Aplicar;
Pronto!

Isso resolveu no meu MAC, provavelmente irá resolver nos demais. Aparentemente é um problema do JAVA 7.

Qualquer dúvida, estou a disposição.
archive
Rank: OraSauro
Rank: OraSauro
Mensagens: 595
Registrado em: Sex, 02 Dez 2016 7:31 am

Efetuei o teste no meu Mac, funcionou.

Obrigado pela dica!
archive
Rank: OraSauro
Rank: OraSauro
Mensagens: 595
Registrado em: Sex, 02 Dez 2016 7:31 am

Selecionar tudo

ALERT: Do not upgrade to JRE 7. End-Users Must Manually Apply JRE 6 Updates [ID 1467815.1]
 
Applies to:
 
Oracle Health Sciences Clinical Development Analytics - Version 2.1 Plus to 2.1 Plus [Release 2.1]
Oracle Life Sciences Data Hub - Version 2.0 and later
Oracle Clinical - Version 4.6.0 and later
Oracle Healthcare Transaction Base - Version 5.0 and later
Oracle Clinical Remote Data Capture Option - Version 4.6.0 and later
Information in this document applies to any platform.
 
Description
All Health Sciences desktop administrators must ensure that End users manually apply JRE 6 updates, and do not upgrade to JRE 7.
 
 
Why is this required?
To ensure that Java Users remain on a secure version, Windows systems that rely on auto-update will be auto-updated from JRE 6 to JRE 7.
If you have Auto-Update enabled, your JRE 1.6 version will be updated to JRE 7.
·          

        This may happen as early as July 3, 2012.
        This will definitely happen after Sept. 7, 2012, after the release of 1.6.0_35 (6u35).

JRE 7 has not been certified with Health Sciences Forms Based Applications -- Oracle Clinical , RDC Classic, TMS , AERS, LSH EBS Administration. These applications will stop working if you upgrade to JRE 7.
Until Health Sciences applications using Oracle Forms are certified with JRE 7, users should not rely on the windows auto-update mechanism for their client machines and should manually keep the JRE up to date with the latest versions of 6 on an ongoing basis.
Occurrence
The following Health Sciences products will be affected if JRE7 is installed: OC, RDC classic, TMS, AERS, LSH, CDA plus, HTB
 
OC
You will not be able to log into the Application.
RDC Classic
You will not be able to log into the Application.
Applications like RDC Onsite, which do not use the JRE plugin, will not be affected.
TMS
You will not be able to log into the Application. TMS Lite will not be affected.
AERS
You will not be able to login into AERS application
CDA plus
CDA Plus is affected, but indirectly. Functioning of CDA would not be affected by upgrading to JRE 7. However, CDA depends on LSH, which in turn uses eBusiness Suite. Upgrading to JRE7 would disable forms used by the EBS administrator to configure EBS. This would prevent carrying configuration changes, and configuration of new EBS installations. In the case that it was necessary to make such changes to EBS on which CDA Plus was running, the upgrade to JRE7 would have an effect on CDA.
CDA Standard is not affected by this bulletin; it does not depend on eBusiness Suite in any way.
LSH
You will not be able to log in to Oracle Applications Profile Forms using the steps described in the section How to Log In to Oracle Applications Profile Forms in the Oracle Life Sciences Data Hub System Administrator's Guide. Core LSH will not be impacted, but changing profile values, concurrent manager tasks, post installation tasks, etc will be impacted.
URGENT BULLETIN: All E-Business Suite End-Users Must Manually Apply JRE 6 Updates
 
HTB
Administrators will not be able to access “System Administrator”/”Profile”/”System"
 
Symptoms
OC/RDC Classic/TMS
When attempting to login to OC, RDC Classic, or TMS, you will get the following error:
FRM-92095: Oracle Jinitiator version too low. Please install version 1.1.8.2 or higher.
For more information on how to recover from this please see note 1468775.1
AERS
When attempting to login to AERS you will get the following error:
You will get a security warning message "An application would like to access an old version of Java"
When you try to click "Continue" or "Cancel" your screen will freeze, or it is possible you will get the "FRM-92095: Oracle Jinitiator version too low" error
For more informationon how to recover from this please see note 1469196.1
 
LSH
When attempting to Select "LSH Setup Admin"/"Setups"/"Lookups", the following error is displayed:
FRM-92095: Oracle Jinitiator version too low. Please install version 1.1.8.2 or higher.
For more informationon how to recover from this please see note 1468041.1
HTB
When attempting to Select “System Administrator”/”Profile”/”System, the following error is displayed:
FRM-92095: Oracle Jinitiator version too low. Please install version 1.1.8.2 or higher.
For more informationon how to recover from this please see note 1468837.1
Workaround
How to avoid the problem:
Ensure that JRE updates are done manually by unchecking the "Check for Updates Automatically" button under the Java Control Panel:
For Windows 7, ensure JRE updates are done manually by either checking the box "Prompt User" or "Never Auto-Download" under the Java Control Panel:
 
What to do if you already upgraded to JRE 7:
If a Health Sciences end-user's desktop has been inadvertently upgraded to JRE 1.7, you must:

     
        Uninstall JRE 1.7
        Reinstall the latest JRE 1.6 release (or the previously installed version).
     
    note : the above de-install and re-install steps are covered in detail in note 1468775.1

Stay on Java 6 for now => Health Sciences customers should continue to run JRE 1.6 (a.k.a. JRE 6) on their Windows end-user desktops.
Patches
History
18-Jun-2012 - Alert updated and made external
Responder
  • Informação
  • Quem está online

    Usuários navegando neste fórum: Nenhum usuário registrado e 9 visitantes