Modelo de Datos Softland Contabilidad y Presupuestos

Modelo de Datos Softland

The post Modelo de Datos Softland Modulo de Contabilidad appeared first on DBAgroup.

C:\Users\fmanriquezo> sqlplus / as sysdba

SQL> show con_name

CON_NAME
------------------------------
CDB$ROOT

SQL> SELECT con_id, name from v$pdbs;

    CON_ID
----------
NAME
--------------------------------------------------------------------------------
         2
PDB$SEED

         3
XEPDB1

SQL> column name format a20
SQL> SELECT con_id, name from v$pdbs;

    CON_ID NAME
---------- --------------------
         2 PDB$SEED
         3 XEPDB1

SQL> SELECT name as "Service name" FROM v$active_services where con_id=3;

Service name
----------------------------------------------------------------
xepdb1

*******TNSNAMES:ORA****************

# tnsnames.ora Network Configuration File: D:\app\fmanriquezo\product\18.0.0\dbhomeXE\NETWORK\ADMIN\tnsnames.ora
# Generated by Oracle configuration tools.

XE =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = LOCALHOST)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = XE)
    )
  )

XEPDB1 =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = LOCALHOST)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = XEPDB1)
    )
  )

LISTENER_XE =
  (ADDRESS = (PROTOCOL = TCP)(HOST = LOCALHOST)(PORT = 1521))


ORACLR_CONNECTION_DATA =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
    )
    (CONNECT_DATA =
      (SID = CLRExtProc)
      (PRESENTATION = RO)
    )
  )

***********LISTENER.ORA****************************

# listener.ora Network Configuration File: D:\app\fmanriquezo\product\18.0.0\dbhomeXE\NETWORK\ADMIN\listener.ora
# Generated by Oracle configuration tools.

DEFAULT_SERVICE_LISTENER = XE

SID_LIST_LISTENER =
  (SID_LIST =
    (SID_DESC =
      (SID_NAME = CLRExtProc)
      (ORACLE_HOME = D:\app\fmanriquezo\product\18.0.0\dbhomeXE)
      (PROGRAM = extproc)
      (ENVS = "EXTPROC_DLLS=ONLY:D:\app\fmanriquezo\product\18.0.0\dbhomeXE\bin\oraclr18.dll")
    )
  )

LISTENER =
  (DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = LOCALHOST)(PORT = 1521))
      (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
    )
  )

lsnrcrt reload

C:\Users\fmanriquezo> lsnrcrl status

LSNRCTL for 64-bit Windows: Version 18.0.0.0.0 - Production on 13-AGO-2019 11:19:14

Copyright (c) 1991, 2018, Oracle. All rights reserved.

Conectßndose a (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=NTB-FMANRIQUEZ.neuronet.cl)(PORT=1521)))
ESTADO del LISTENER
------------------------
Alias LISTENER
Versi¾n TNSLSNR for 64-bit Windows: Version 18.0.0.0.0 - Production
Fecha de Inicio 12-AGO-2019 12:06:14
Tiempo Actividad 0 dÝas 23 hr. 13 min. 6 seg.
Nivel de Rastreo off
Seguridad ON: Local OS Authentication
SNMP OFF
Servicio por Defecto XE
Parßmetros del Listener D:\app\fmanriquezo\product\18.0.0\dbhomeXE\network\admin\listener.ora
Log del Listener D:\app\fmanriquezo\product\18.0.0\diag\tnslsnr\NTB-FMANRIQUEZ\listener\alert\log.xml
Recibiendo Resumen de Puntos Finales...
 (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=NTB-FMANRIQUEZ.neuronet.cl)(PORT=1521)))
 (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1521ipc)))
 (DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=127.0.0.1)(PORT=5500))(Security=(my_wallet_directory=D:\APP\FMANRIQUEZO\PRODUCT\18.0.0\admin\XE\xdb_wallet))(Presentation=HTTP)(Session=RAW))
Resumen de Servicios...
El servicio "CLRExtProc" tiene 1 instancia(s).
 La instancia "CLRExtProc", con estado UNKNOWN, tiene 1 manejador(es) para este servicio...
El servicio "XE" tiene 1 instancia(s).
 La instancia "xe", con estado READY, tiene 1 manejador(es) para este servicio...
El servicio "XEXDB" tiene 1 instancia(s).
 La instancia "xe", con estado READY, tiene 1 manejador(es) para este servicio...
El servicio "df7555b53690479bb2b206c906bcabfb" tiene 1 instancia(s).
 La instancia "xe", con estado READY, tiene 1 manejador(es) para este servicio...
El servicio "xepdb1" tiene 1 instancia(s).
 La instancia "xe", con estado READY, tiene 1 manejador(es) para este servicio...
El comando ha terminado correctamente

SQL> ALTER SESSION SET CONTAINER=XEPDB1;

sesion modificada

SQL> column username format a25;
SQL> select username, account_status from dba_users;

USERNAME                  ACCOUNT_STATUS
------------------------- --------------------------------
SYS                       OPEN
SYSTEM                    OPEN
XS$NULL                   EXPIRED & LOCKED
LBACSYS                   LOCKED
OUTLN                     EXPIRED & LOCKED
DBSNMP                    EXPIRED & LOCKED
APPQOSSYS                 EXPIRED & LOCKED
DBSFWUSER                 EXPIRED & LOCKED
GGSYS                     EXPIRED & LOCKED
ANONYMOUS                 EXPIRED & LOCKED
HR                        EXPIRED & LOCKED

USERNAME                  ACCOUNT_STATUS
------------------------- --------------------------------
CTXSYS                    EXPIRED & LOCKED
DVSYS                     LOCKED
SI_INFORMTN_SCHEMA        EXPIRED & LOCKED
DVF                       LOCKED
GSMADMIN_INTERNAL         EXPIRED & LOCKED
ORDPLUGINS                EXPIRED & LOCKED
MDSYS                     EXPIRED & LOCKED
OLAPSYS                   EXPIRED & LOCKED
ORDDATA                   EXPIRED & LOCKED
XDB                       EXPIRED & LOCKED
WMSYS                     EXPIRED & LOCKED

USERNAME                  ACCOUNT_STATUS
------------------------- --------------------------------
ORDSYS                    EXPIRED & LOCKED
GSMCATUSER                EXPIRED & LOCKED
MDDATA                    EXPIRED & LOCKED
SYSBACKUP                 EXPIRED & LOCKED
REMOTE_SCHEDULER_AGENT    EXPIRED & LOCKED
PDBADMIN                  OPEN
GSMUSER                   EXPIRED & LOCKED
SYSRAC                    EXPIRED & LOCKED
OJVMSYS                   LOCKED
AUDSYS                    LOCKED
DIP                       EXPIRED & LOCKED

USERNAME                  ACCOUNT_STATUS
------------------------- --------------------------------
SYSKM                     EXPIRED & LOCKED
ORACLE_OCM                EXPIRED & LOCKED
SYS$UMF                   EXPIRED & LOCKED
SYSDG                     EXPIRED & LOCKED

37 filas seleccionadas.

SQL> alter user hr identified by "hr" account unlock;

Usuario modificado.

sqlplus usuario/passwd@//localhost:1521/xepbd1

C:\Users\fmanriquezo> sqlplus hr/hr@//localhost:1521/xepdb1

SQL*Plus: Release 18.0.0.0.0 - Production on Mar Ago 13 12:03:30 2019
Version 18.4.0.0.0

Copyright (c) 1982, 2018, Oracle.  All rights reserved.


Conectado a:
Oracle Database 18c Express Edition Release 18.0.0.0.0 - Production
Version 18.4.0.0.0

SQL> column tname format a26
SQL> select * from tab;

TNAME                      TABTYPE        CLUSTERID
-------------------------- ------------- ----------
REGIONS                    TABLE
COUNTRIES                  TABLE
LOCATIONS                  TABLE
DEPARTMENTS                TABLE
JOBS                       TABLE
EMPLOYEES                  TABLE
JOB_HISTORY                TABLE
EMP_DETAILS_VIEW           VIEW

8 filas seleccionadas.

XEPDB1 =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = LOCALHOST)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = xepdb1)
    )
  )

C:\Users\fmanriquezo>sqlplus hr/hr@xepdb1

SQL*Plus: Release 18.0.0.0.0 - Production on Mar Ago 13 12:41:49 2019
Version 18.4.0.0.0

Copyright (c) 1982, 2018, Oracle.  All rights reserved.

Hora de ultima Conexi¾n Correcta: Mar Ago 13 2019 12:03:30 -04:00

Conectado a:
Oracle Database 18c Express Edition Release 18.0.0.0.0 - Production
Version 18.4.0.0.0

SQL> SHOW USER

The post Oracle 18C express Edition. Como conectarse a la PDB xepdb1 y desbloquear usuario HR appeared first on DBAgroup.

Today I wanted to share with you my personal approach for how to get into the details on AWR Report and where to see and where should be our attention. Keep in mind just two main focuses : the Application and the Database instance

1) Application: Most of the times you should go directly to review how was the SQL statements Performance. That is MANDATORY and the result of your analysis will be the classic TOP 10 SQL with the worst performance. That should be called : Oracle Application’s Performance Tuning .

2) Instance: read once, twice or three times the AWR looking for issues. What kind of issues or metrics ?

For example here I have  a Conclusion and Workaround for one database instance issue regarding performance :

1) Tuning recommendations for PROD-ACME  database instance:

• Based on the statistics of  I/O per event within the database  I recommended :
  • I saw  that for a total of  22MB most of the times their waits are due to lack of buffers cache  (used to put there disk blocks with table’s data) with the rows used. I found 86% of wait events are due this event for the database instance.
  • Action Item: Need to increase  of MB for buffers cache within the database in order to increase the available blocks and space in memory to keep the most used rows there.
  • How much ? In order to see how much we need to increase my recommendation is to put DB_CACHE_ADVICE initialization parameter to ON. Then review (after some weeks) and query the V$DB_CACHE_ADVICE system view so there you will get what is the optimal point to set buffers cache for this instance. (That Advisor was a new feature of 9i release) .

e.g. Waits and What Represents.

What does it mean ?

• So you can see above that WAITS amount of Buffer Cache Reads represents the 85% of Waits for this instance.  In this case this was one of the bottlenecks.

2) Tuning recommendations for ERP  ACME Suite and Customs Applications :

Let’s see next section of the same example …as follows :

Based on the “awrrpt_1_12809_12883.html“ that I got here in my desk I reviews this section to see top 5 events of waits :

Top 5 Timed Foreground Events

,those numbers represent  :

(Good Catch!)  Said that, let’s analyze those  db wait events :

Event 1: DB FILE SEQUENTIAL READ :

These waits usually indicate a single block read (e.g. Idex full scan : an index read with order by clause).

Causes and solutions :

1. Use of unselective index. Solution: 1) Check indexes on the table to ensure that the right index is being use, 2) Check the column order of the index with the WHERE clause of the Top SQL statements

2.  Index Fragmentation: If the DBA_INDEXES.CLUSTERING_FACTOR of the index approaches the number of blocks in the table, then most of the rows in the table are ordered. This is desirable.  However, if the clustering factor approaches the number of rows in the table, it means the rows in the table are randomly ordered and thus it requires more I/Os to complete the operation.

Solution:1) You can improve the index’s clustering factor by rebuilding the table so that rows are ordered according to the index key and rebuilding the index thereafter.

3. High I/O on particular disk or mountpoint. Solution:1) Use in partitioning to reduce the amount of blocks being visited, 2) Make sure optimizer statistics are up to date, 3) Relocate ‘hot’ datafiles :    Place the tables used in SQL statement on a faster part of the disk. 4) Consider the usage of multiple buffer pools and cache frequently used indexes/tables in the KEEP pool, 5) Inspect the execution plans of the SQL statements that access data through indexes, 6) Tune the I/O subsystem
to return data faster.

4. Bad application design – (1^st section of the Perf.tuning report). Solution: 1) Optimize the SQL statement that initiated most of the waits. The goal is to minimize the number of physical and logical reads.Inspect the execution plans of the SQL statements that access data through indexes

1.1).     Examine the SQL statement to see if a). it is doing a full-table scan when it should be using an index, b). it is using a wrong index or c). it can be rewritten to reduce the amount of data it retrieves d). it is appropriate for the SQL statements to access data through index lookups or would full table scan be more efficient? E). the statements use the right drivin table i.e. join order is proper?

5. Range scans on data spread in many different blocks. Solution: 1) check that range scans should not be using reverse indexes. 2)Load the data in sorted manner on the colums on which range scans will be there.

6.  Consider increasing the buffer cache to see if the expanded size will accommodate the additional blocks, therefore reducing the I/O and the wait.

Event 2: DB FILE SCATTERED READS :

This is a wait for multiple blocks to be read concurrently from disk.

Waits for multiple blocks (up to DB_FILE_MULTIBLOCK_READ_COUNT) to be read from disk while performing FTS  / Index fast full scans (no order by) .

Causes:

This wait is encountered because:1) As FTSs are pulled into memory, they are scattered throughout the buffer cache , since it is highly unlikely that they fall into contiguous buffers.2) Since a large number of blocks have to be read into the buffer cache, server process has to search for a large no. of free/usable blocks in buffer cache which leads to waits.

..and Solutions

– May try to cache frequently used small tables to avoid reading them into the memory over and over again.

– Need to optimize multi-block I/O by setting the parameter DB_FILE_MULTIBLOCK_READ_COUNT

– Need to use partition pruning: Partition tables/indexes so that only a partition is scanned each time.

– May you need to consider the usage of multiple buffer pools.

– Need to optimize the SQL statements that initiated most of this waits. We need to minimize the # of physical&logical reads.

For instance the developer need to ask as follows:

Should the SQL statement access the data by a FTS  or index FFS? Or would an index range or unique scan  be more efficient? Or does the query use a right driving table? Or are the SQL predicates appropriate for hash or merge join? Or ,  If FTSs are appropriate, can parallel query improve the RT (response time)?

We need to make sure all statistics are representative of the actual data. Check the LAST_ANALYZED date (I already checked).

The GOAL is :  to reduce the demands for the logical and physical I/Os, and this is best achieved through SQL/Application tuning.

3) Tuning recommendations for Data Access (how to store the information within the Oracle Database).

Typical objections: Your suggestion to have different block sizes to some tables is not good for OLTP databases. We need to create tablespaces with different block sizes and also different buffer cache for each block size. For this, we need to reduce the cache area for some tables and provide this area to another. So, depending of the situation, we know that OLTP transactions are small and with short duration and for this reason we need a optimal block size. If we increase the block size we can increase the I/O for these small transactions because for each read operation need to processes more data. For OLAP transaction that uses larger block sizes, the situation is different and almost all the SQLs process a lot of data and for this reason larger block sizes is better.

What can I do ? What can I say ?

That is IDEAL In a perfect world …and I would say : YES. I AGREE.

…but we are living in a normal world (with unperfect people) …and I would add that both the OLTP and OLAP systems have to coexist within the same database so we need to realize that in this world with this people you should analyze CASE by CASE and make a decision.

Most of the database today are running OLTP and OLAP in a mixed environment. No chance for normalizations within the OLAP tables and yes, small blocks used to store the data wont have good  performance.

In the other hand is also true that big blocks used for OLTP tables will create unnecessary problems.

Good or not it is a trend in the Data warehousing today…and is a technology challenge.

(Those are my 2 cents for today).

Jorge Acevedo

The post HOW TO: Analyzing and Interpreting AWR Report appeared first on DBAgroup.

….

But we can generate it using SQLPLUS as well :

AWR Snapshot Reports
Oracle provides reports that you can run to analyze the data in the AWR. These reports are much like the statspack reports prior to Oracle Database 10g. There are two reports: awrrpt.sql and awrrpti.sql, which are available in the directory $ORACLE_HOME/ rdbms/ admin.
The output of these reports is essentially the same, except that awrrpti.sql script allows you to define a specific instance to report on. The reports are much like the statspack reports of old, in that you define a beginning and ending snapshot ID, and the output filename of the report. Additionally, you can opt to produce the report in either text format or HTML format.

[oaPROD usa.com01 PROD] $ sqlplus ‘/as sysdba’
SQL> @awrrpt.sql

Current Instance   DB Id    DB Name      Inst Num Instance

———– ———— ——– ————
Specify the Report Type
~~~~~~~~~~~~~~~~~~~~~~~
Would you like an HTML report, or a plain text report?Enter ‘html’ for an HTML report, or ‘text’ for plain textDefaults to ‘html’
Enter value for report_type: text

Type Specified:  text Instances in this Workload Repository schema
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DB Id     Inst Num DB Name      Instance     Host
———— ——– ———— ———— ————
01  1141957891        1 PROD        PROD        usa.com
02 1141957891        1 GLD1        LGLD1        ind.com

Using  124707144 for database Id Using 1 for instance number Specify the number of days of snapshots to choose from
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Entering the number of days (n) will result in the most recent(n) days of snapshots being listed.  Pressing <return> withoutspecifying a number lists all completed snapshots.  Enter value for num_days: 1

Listing the last day’s Completed Snapshots

SnapInstance     DB Name        Snap Id    Snap Started    Level
———— ———— ——— —————— —–
PROD        PROD
6400 14 Oct 2008 00:01      1

6401 14 Oct 2008 01:00      1

6402 14 Oct 2008 02:00      1

6403 14 Oct 2008 03:00      1

6404 14 Oct 2008 04:00      1

6405 14 Oct 2008 05:01      1
Specify the Begin and End Snapshot Ids
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Enter value for begin_snap: 6412

Begin Snapshot Id specified: 6412

Enter value for end_snap: 6413

End   Snapshot Id specified: 6413

Specify the Report Name
The default report file name is awrrpt_1_6412_6413.txt.  To use this name,press <return> to continue, otherwise enter an alternative.

Enter value for report_name:End of ReportReport written to awrrpt_1_6412_6413.txt

————-

You can see what snapshots are currently in the AWR by using the DBA_HIST_SNAPSHOT view as seen in this example:
SQL> SELECT snap_id, begin_interval_time, end_interval_time  FROM dba_hist_snapshot ORDER BY 1;

J.

The post AWR Report – How to get it through EM appeared first on DBAgroup.

You have to use OUI to check whether Oracle Secure Enterprise Search is installed or not.

TIP: Start Oracle Universal Installer from your system prompt (UNIX) with the following command:

./runInstaller

2)From v$option:

SQL> set pages 100

SQL> select * from v$option;

PARAMETER                                                        VALUE

—————————————————————- —–

Partitioning                                                     TRUE

Objects                                                          TRUE

Real Application Clusters                                        FALSE

Advanced replication                                             TRUE

Bit-mapped indexes                                               TRUE

Connection multiplexing                                          TRUE

Connection pooling                                               TRUE

Database queuing                                                 TRUE

Incremental backup and recovery                                  TRUE

Instead-of triggers                                              TRUE

Parallel backup and recovery                                     TRUE

Parallel execution                                               TRUE

Parallel load                                                    TRUE

Point-in-time tablespace recovery                                TRUE

Fine-grained access control                                      TRUE

Proxy authentication/authorization                               TRUE

Change Data Capture                                              TRUE

Plan Stability                                                   TRUE

Online Index Build                                               TRUE

Coalesce Index                                                   TRUE

Managed Standby                                                  TRUE

Materialized view rewrite                                        TRUE

Materialized view warehouse refresh                              TRUE

Database resource manager                                        TRUE

Spatial                                                          TRUE

Visual Information Retrieval                                     TRUE

Export transportable tablespaces                                 TRUE

Transparent Application Failover                                 TRUE

Fast-Start Fault Recovery                                        TRUE

Sample Scan                                                      TRUE

Duplexed backups                                                 TRUE

Java                                                             TRUE

OLAP Window Functions                                            TRUE

Block Media Recovery                                             TRUE

Fine-grained Auditing                                            TRUE

Application Role                                                 TRUE

Enterprise User Security                                         TRUE

Oracle Data Guard                                                TRUE

Oracle Label Security                                            FALSE

OLAP                                                             TRUE

Table compression                                                TRUE

Join index                                                       TRUE

Trial Recovery                                                   TRUE

Data Mining                                                      TRUE

Online Redefinition                                              TRUE

Streams Capture                                                  TRUE

File Mapping                                                     TRUE

Block Change Tracking                                            TRUE

Flashback Table                                                  TRUE

Flashback Database                                               TRUE

Data Mining Scoring Engine                                       FALSE

Transparent Data Encryption                                      TRUE

Backup Encryption                                                TRUE

Unused Block Compression                                         TRUE

54 rows selected.

—

TRUE mean we can use that option and FALSE mean we can’t.

3)From DBA_REGISTRY:

SQL> select comp_name, status from dba_registry;

COMP_NAME                                                              STATUS

---------------------------------------------------------------------- -----------

Oracle Database Catalog Views                                          VALID

Oracle Database Packages and Types                                     VALID

Oracle Workspace Manager                                               VALID

JServer JAVA Virtual Machine                                           VALID

Oracle XDK                                                             VALID

Oracle Database Java Packages                                          VALID

Oracle Expression Filter                                               VALID

Oracle Data Mining                                                     VALID

Oracle Text                                                            VALID

Oracle XML Database                                                    VALID

Oracle Rules Manager                                                   VALID

Oracle interMedia                                                      VALID

OLAP Analytic Workspace                                                VALID

Oracle OLAP API                                                        VALID

OLAP Catalog                                                           VALID

Spatial                                                                VALID

Oracle Enterprise Manager                                              VALID

17 rows selected.

Database queuing
This Integrates a message queue system with the database.

In the table DBA_REGISTRY the status may be,

1)INVALID : Some problem in it.

2) VALID: Working properly

3) LOADING:The component is loading.

4) LOADED: The component just loaded.

5) UPGRADING:The component is in a process of upgrade.

6) UPGRADED:The component has been upgrade.

7) DOWNGRADING:The component is in a process of downgrade.

8) DOWNGRADED:The component has been downgraded.

9) REMOVING:Someone is uninstalling the component.

10)REMOVED:The component has been unistalled.

That’s all!

J.

The post HOWTO: Checking options installed within the Database/Oracle Home appeared first on DBAgroup.

A.      When the forms are changed to socket mode:

1.      Will this affect the EBS application in anyway (will it be slow than now)

2.      Do we need to perform any change on our or the workstation’s side ?

ASSESSMENT AND SOLUTION

Please look at the Note in Metalink 310976.1. It seems that the Java Console in JInitiator tells you at the beginning which mode you are using.

Verifying the Forms Client Connection to the Forms Server

Once the Applet has initialized and started, it connects to the Forms Listener, using the serverPort, serverHost and connectMode parameters displayed in the Java console.  Steps to verify this are:

Check the serverPort port number and specified serverHost are correct

Verify the connectMode. In Applications 11i, the Forms Server must be started with the same connectMode (Socket, HTTP or HTTPS).

Socked mode is the standard…and:

1. When the forms are changed to socket mode:

https://blogs.oracle.com/stevenChan/entry/which_is_better_forms_servlet_or_socket_mode

1. Will this affect the EBS application in anyway (will it be slow than now)

No way.

2.      Do we need to perform any change on our or the workstation’s side ?

Nope. Only the Midtier servers where forms is running

Just change a file like this:

/pfoxxi/applmgr/common/html/bin/appsweb_PFOXXI_auohsfoxx03.cfg

, and then bounce and that’s all.

MI EXPLICACION

Para mi la principal diferencia radica en como se establece el trafico a nivel ISO OSI si comparamos TCP Socket con Web Sockets.

Websockets difiere principalmente de TCP Sockets porque Websockets habilita una suerte de corriente de mensajería en vez de habilitar tan solo una corriente de bytes, me explico :

Cuando envias bytes desde un buffer por un socket TCP normal, la función de envío devuelve el número de bytes que se enviaron del búfer. Si se trata de non-blocking socket or de un envio no bloqueable , entonces el número de bytes que se envían puede ser menor que el tamaño del bufer. Si se trata de un blocking socket o un envio blockeable, entonces, el número devuelto coincidira con el tamaño del bufer, pero la llamada puede bloquearse . Con WebSockets , los datos que se pasan al método de envío son siempre enviados como un «mensaje», osea, se envía todo o nada en absoluto. Además , las implementaciones de WebSocket del navegador no bloquean la llamada de envío.

Pero hay diferencias más importantes que se encuentran en el lado de la recepción. Cuando el receptor hace una recv ( o lectura ) en un socket TCP , no hay garantía de que el número de bytes retornado corresponda a una solo envio ( o a una sola escritura ) en el lado del remitente. Puede ser que sea el mismo envio, pueden ser menos bytes (o cero bytes) y que incluso podrían ser más bytes (en cuyo caso bytes de múltiples envios / escrituras se estarán recibiendo ) . Con WebSockets , la recepción de un mensaje es manejado por eventos (tu generalmente registras una rutina controladora de mensajes ) ??, y los datos manejados por el evento son siempre el mensaje completo que la otra parte ha enviado.

Tengan en cuenta que tu puedes hacer la comunicación basada en mensajes utilizando sockets TCP , pero se necesita una capa extra/encapsulamiento que agrege datos de calce de las partes/mensajes para los mensajes de esa manera los mensajes originales se pueden volver a montar en las piezas. De hecho , WebSockets está construido sobre Sockets TCP normales y utiliza cabeceras de trama que contienen el tamaño de cada trama y las cuales indican que frames son parte de un mensaje . La API de WebSocket re-ensambla los fragmentos TCP de datos en los frames/tramas que son ensamblados en los mensajes antes de invocar el controlador de eventos de mensaje , lo que se hace una vez por mensaje.

Esta seria la conversación Cliente-Servidor de TCP Sockets

http://www.eg.bucknell.edu/~cs315/Spring12/wordpress/wp-content/uploads/2012/02/tcplab.png

The post Forms in socket mode appeared first on DBAgroup.

The statement extracts all the active assignments of responsibilities by using the FND_USER_RESP_GROUPS table which combines DIRECT and INDIRECT responsibilities.

If you need only the DIRECT responsibilities than you also have the option to use the seeded view FND_USER_RESP_GROUPS_DIRECT. If you need only the INDIRECT responsibilities (added by roles – like Application Diagnostics and others) than use the seeded view FND_USER_RESP_GROUPS_INDIRECT.

As always adjust the SQL to cover your needs.

SELECT
fuser.USER_NAME USER_NAME
, per.FULL_NAME FULL_NAME
, per.EMPLOYEE_NUMBER EMPLOYEE_NUMBER
, frt.RESPONSIBILITY_NAME RESPONSIBILITY
FROM
FND_USER fuser
, PER_PEOPLE_F per
, FND_USER_RESP_GROUPS furg
, FND_RESPONSIBILITY_TL frt
WHERE
fuser.EMPLOYEE_ID = per.PERSON_ID
AND fuser.USER_ID = furg.USER_ID
AND (to_char(fuser.END_DATE) is null
OR fuser.END_DATE > sysdate)
AND frt.RESPONSIBILITY_ID = furg.RESPONSIBILITY_ID
AND (to_char(furg.END_DATE) is null
OR furg.END_DATE > sysdate)
AND frt.LANGUAGE = ‘US’
ORDER BY
, fuser.USER_NAME;

I hope this will be useful.

J.

The post HOWTO : Getting User Responsability on EBS 11i using a Database user (BOLINF or APPS) appeared first on DBAgroup.

In this article, the SQL script that implements the creation of these relational structures is developed and adapted  for Oracle Database. This script is based on the script worked by Hjalmtyr Hafsteinsson for PostgreSQL database.

The script does the following tasks

Cleans Sailors Schema and tablespaces of previous script executions

Creates Sailors_data and Sailors_index  tablespaces

Creates Sailors Schema

Grants roles and privileges to Sailors user

Connects to Sailors user

Creates tables, constraints,  in the Sailors Schema

Populates tables

Adds new columns  and new constraints (that are not part of the original data model)

Creates B-tree indexes for columns that are used in WHERE clause

The figure below shows the Sailors data model. It was developed using Oracle SQL Data Modeler

Sailors Model

Finally, in the following link, you can see the Sailors SQL Script

SailorsSchemaOracle3

The post Ramakrishnan & Gehrke Sailors script for Oracle database appeared first on DBAgroup.

La solucion que voy a postear es una de las muchas que encontre en este link : http://msutic.blogspot.com/2009/06/truncating-rotating-flushing.html

La solución que implemente fue en un Oracle 10.2.0.5 y consistia en crear un nuevo log para el listener por cada mes del año con el siguiente formato :listener_yyyymm.log , asi cada mes del año iba a tener su propio log.

Estos son los pasos :

1) Conectarse con el utilitario LSNRCTL y setear el listener actual (Por lo general el nombre default es LISTENER)

C:UsersJCAJ>lsnrctl

LSNRCTL> set current_listener LISTENER

Current Listener is LISTENER

2) Luego setear el logfile por le nombre que deseamos , en este caso listener_201309.log

LSNRCTL> set log_file listener_201309.log

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))

LISTENER parameter «log_file» set to listener_201309.log

The command completed successfully

3 ) Con lo anterior el log que habia antes «listener.log» ha dejado de ser utilizado, y ahora es listener_201309.log el que esta funcionado como log para el listener, para esto confirmamos con un lsnrctl status y vemos la fila que tiene el parametro Listener Log File :

4) Como paso final se van a grabar los cambios realizados al listener.ora, por que en caso que el servidor se apage de forma abrupta o se reinicie el listener este va a comenzar a grabar nuevamente en el log default, y no es lo que queremos. Estos cambios los podemos grabar desde la misma herramienta lsnrctl, la que al grabar los cambios va a dejar un respaldo en la carpeta donde este el log con la configuracion del listener.ora anterior.

LSNRCTL> save_config

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))

Saved LISTENER configuration parameters.

Listener Parameter File   C:appJCAJproduct11.2.0dbhome_1networkadminlistener.ora

Old Parameter File   C:appJCAJproduct11.2.0dbhome_1networkadminlistener.bak

The command completed successfully

5) Ahora si vamos a revisar el archivo listener.ora al final de este va a aparecer la hora de cambio y el parametro para que en caso que se reinicie siga escribiendo en el log correcto :

#—-ADDED BY TNSLSNR 06-SEP-2013 11:32:48—

LOG_FILE_LISTENER = listener_201309.log

#——————————————–

Bueno , despues de todo esto el log original podria ser borrado o archivado.

En el link que comente en el principio, hay mas soluciones en caso de que estemos en un escenario en que el listener no se puede bajar.

Esto sirve para las base de datos Oracle 10g en adelante, pero hay que recordar que 11g viene con un sistema que es el Automatic Diagnostic Repository (ADR).

The post Cambiar logfile del Listener sin tener que detenerlo appeared first on DBAgroup.

The post Paquete LT_CTX_PKG inválido (9.2.0.8) appeared first on DBAgroup.