Skip to main content

What is JAVA ?

Java was originally developed by Sun Microsystems which and was initiated by James Gosling and released in 1995 as core component .
The latest version of the Java Standard Edition is Java SE 8. With the widespread popularity, multiple configurations were built to suit for various types of platforms. e.g.: J2EE for Enterprise Applications, J2ME for Mobile Applications.
There is new J2 versions were renamed as Java SE, Java EE, and Java ME respectively. As we know Java is guaranteed to be Write Once, Run Anywhere :).


So what is java? 

Java is a Technology :) Below are the features − 
  • Object Oriented − For Java and in JAVA everything is an Object. So ItJ can be easily extended because it is based on the Object model.
  • Platform Independent (WOW) − SO like many other programming languages like C and C++, when Java is compiled, it is not compiled into platform specific machine That's why its called Platform independent language, It is compiled into platform independent byte code. This code is distributed and interpreted by the Virtual Machine (JVM) .
  • Simple and Portable  − Actully Java is designed to be easy to learn to all that's the reason it's very famous among all. All you need to is to master the concepts of OOP Java.It's also very easily portable because it has no implementaion dependency. 
  • Secure Like anything −  Java is  secure and it's security feature  enables to develop a virus-free and temper free systems. 
  • Robust −  So Java Checks for the error on the compile time and also on runtime checking.

    Multithreaded − It means  with this feature of JAVA, You can write a code to perform multiple tasks at same time.  
  • High Performance − Java uses Just-In-Time compilers,So that automatically enables high performance.
  • Distributed − Java is mainly designed for the distributed environment of the internet.
  • Dynamic − Java more dynamic than C or C++.


    Keep Sharing :)

Labels:

Comments

Post a Comment

Popular posts from this blog

DBA_SCHEDULER_JOB_RUN_DETAILS and PURGE_LOG

How to purge DBA_SCHEDULER_JOB_RUN_DETAILS? Manually deleting from DBA_SCHEDULER_JOB_RUN_DETAILS is not recommended by oracle.DBA_SCHEDULER_JOB_RUN_DETAILS is a view that is using two master tables (scheduler$_job_run_details and scheduler$_event_log) and display the information about jobs history. As there is one procedure named PURGE_LOG and Oracle have Scheduler for this procedure. It will purges all rows in the job log that are older than 30 days.This is the default behavior of this procedure. You can change this to any number of days you want by setting the attribute "SET_SCHEDULER_ATTRIBUTE". e.g. exec DBMS_SCHEDULER.SET_SCHEDULER_ATTRIBUTE('log_history','15'); It will purge all logs older than 15days and it will maintain the history of 15days. But If you want manually purge these logs, you can use below solution:- exec DBMS_SCHEDULER.PURGE_LOG(log_history => 15, which_log => 'JOB_LOG'); It will purge all entries from the jog log that are o...
Post a Comment
Read more

ORA-02051 Another Session Or Branch In Same Transaction Failed

ORA-02051 Another Session Or Branch In Same Transaction Failed (Doc ID 2253226.1)          SYMPTOMS for ORA-02051 Another Session Or Branch In Same Transaction Failed. Database performance is slow and caused   the transactions ORA-02051 another session or branch in same transaction failed or finalized CAUSE for ORA-02051 Another Session Or Branch In Same Transaction Failed. Session transactions branches caused the issue Excessive Waits On The Event "Global transaction acquire instance locks" SOLUTION Please use below sql and identified underscore parameter values for ORA-02051 Another Session Or Branch In Same Transaction Failed : SQL> select a.ksppinm "Parameter", b.ksppstvl "Session Value",c.ksppstvl "Instance Value"  FROM x$ksppi a,x$ksppcv b, x$ksppsv c  WHERE a.indx = b.indx AND a.indx = c.indx AND a.ksppinm LIKE '/_%' escape '/'  AND (a.ksppinm like '%clusterwide_global%' or a.ksppinm like '%disable_autotune_...
Post a Comment
Read more

ORA-65016: FILE_NAME_CONVERT must be specified

ORA-65016: FILE_NAME_CONVERT must be specified I just started working on 12C version of oracle database.It's new to me and facing many problems. Error code: ORA-65016: FILE_NAME_CONVERT must be specified Description:"ORA-65016: FILE_NAME_CONVERT must be specified" normally occurs when you create a PDB.I will explain later what is a PDB. Cause and solution :  ORA-65016: FILE_NAME_CONVERT must be specified caused when Data files, and possibly other files, needed to be copied as a part of creating a pluggable database.Enable OMF or define PDB_FILE_NAME_CONVERT system parameter before issuing CREATE PLUGGABLE DATABASE statement, or specify FILE_NAME_CONVERT clause as a part of the statement and make sure the path you are giving to convert the file exists. I think if you are creating the PDB's using GUI then you will not face this error "ORA-65016: FILE_NAME_CONVERT must be specified". If you creating ODB using script and you have gave a wrong path then may you f...
2 comments
Read more